That's right weird, unzwar I've created a Minecraft server, released the port and made everything possible so that my friends can connect. But as soon as I enter my IP in the server properties and start the server there's Failed to bind to port but if I do not specify Ip the server starts but my friends can't connect where is the whole time Connect to the server.
You should not enter IP because you have no static IP in your home.
Just leave it empty, then everything should work.
But as soon as I enter my IP in the server properties
Then try out there with 0.0.0.0
Unless the server takes an empty indication (for whatever reason) 127.0.0.1 as the default value.
He should also take 127.0.0.1, that's localhost.
Should not he just.
If it takes 127.0.0.1, the server will only accept connections from itself. And that leads exactly to the effect described in the question…
I have, there's Starting Minecraft Server on 0.0.0.0:25565 but my friends still can't connect.
That's the problem, that's not it.
How did you set up the haven release?
Example scenario:
The PC on which the server is running has the local IP 192.168.0.123
The port used is 25565 (TCP)
Then the port release must be "port 25565 (TCP) to 25565 (TCP) after 25565 (TCP) for 192.168.0.123".
To connect from the outside then the IP is used, which you e.g. Learn with http://httpbin.org/ip or what would be even better: with the DynDNS hostname (previously set up) (for example, using https://noip.com).
I released the port with UDP as well as with TCP from 25565 to 25565, perhaps I should not release the haven with UDP?
Besides, I had already used that with noip (Duc). I uninstalled it because I thought that might be because of it
My server properties look like this:
spawn-protection = 0
max-tick-time = 60000
query.port = 25565
generator-settings =
force-game mode = false
allow-nether = true
enforce-whitelist = false
game mode = survival
broadcast console-to-ops = true
enable-query = false
player-idle-timeout = 0
difficulty = normal
spawn-monsters = true
broadcast rcon-to-ops = true
op-permission-level = 4
pvp = true
snooper-enabled = true
level-type = default
hardcore = false
enable-command-block = false
max-players = 20
network-compression threshold = 256
resource-pack-sha1 =
max-world-size = 29999984
function-permission-level = 2
rcon.port = 25575
server-port = 25565
server-ip =
spawn npcs = true
allow-flight = false
level-name = world
view-distance = 10
resource-pack =
spawn-animals = true
white-list = false
rcon.password =
generate-structures = true
online-mode = true
max-build height = 256
level-seed =
prevent-proxy-connections = false
use-native-transport = true
motd = A Minecraft Server
enable-rcon = false
Okay, I researched something again:
The port must be shared with both TCP and UDP.
The entry for server-ip should be left empty, unless you want to "randomly" make a very "special" constellation (for example, if the server should only be accessible on the local network).
Noip or The DUC is less the source than more of a solution to the problem.
If it still does not work, there are 2 possible causes left:
You have somewhere in the port release a faulty setting.
Your ISP does not support port shares (for example, if you also hangs on the provider side on a NAT system or similar).
Minecraft vanilla, bukkit and spigot are luckily 0.0.0.0
Try to specify your internal IP. If you have released the ports and the firewall does not block anything the rest should be done by the router. By internal IP I mean e.g. 192.168.0.11 (usually starts with 192.168)
