BDS-10608Can't connect from non-local networks (outside of LAN)
Getting very strange behaviour:
All my other apps deployed on my LAN (and even on the same server, also running in docker) work fine, I work in devops for a living, I know how to configure my firewall, that isn't a problem. I know a lot of issues here are random users posting unrelated issues, but this isn't it. With that out of the way, here are some details of my setup:
- Running inside of a docker container, forwarding the UDP port for the server to the host
- If I connect over LAN on a client, it works fine
- If I try to connect using the public IP or DNS name, I get an "unable to connect to world"
- Using the public name/ip, the server DOES receive and reply to single UDP packets, presumably ones that are just pings to show in the client UI
- Using the public name/ip, I can go to this site and it will connect and read the info of the server
- The server itself (not just the container, but the host machine) doesn't receive further packets once the client tries to connect
This makes a whole lot of no sense. It DOES know where the server is, and it DOES connect to get some metadata, but refuses to connect for a game session.
This is a snippet from the container logs:
bedrock | [INFO] IPv4 supported, port: 19132 bedrock | [INFO] IPv6 not supported bedrock | [INFO] IPv4 supported, port: 45410 bedrock | [INFO] IPv6 not supported bedrock | [INFO] Server started.
Not sure what that extra port is, but it shouldn't matter because docker IS NOT forwarding that other port, and local connections work fine despite that.
Created Issue:
Can't connect from non-local networks (outside of LAN)
Getting very strange behaviour:
All my other apps deployed on my LAN (and even on the same server, also running in docker) work fine, I work in devops for a living, I know how to configure my firewall, that isn't a problem. I know a lot of issues here are random users posting unrelated issues, but this isn't it. With that out of the way, here are some details of my setup:
- Running inside of a docker container, forwarding the UDP port for the server to the host
- If I connect over LAN on a client, it works fine
- If I try to connect using the public IP or DNS name, I get an "unable to connect to world"
- Using the public name/ip, the server DOES receive and reply to single UDP packets, presumably ones that are just pings to show in the client UI
- Using the public name/ip, I can go to this site and it will connect and read the info of the server
- The server itself (not just the container, but the host machine) doesn't receive further packets once the client tries to connect
This makes a whole lot of no sense. It DOES know where the server is, and it DOES connect to get some metadata, but refuses to connect for a game session.
This is a snippet from the container logs:
bedrock | [INFO] IPv4 supported, port: 19132 bedrock | [INFO] IPv6 not supported bedrock | [INFO] IPv4 supported, port: 45410 bedrock | [INFO] IPv6 not supported bedrock | [INFO] Server started.Not sure what that extra port is, but it shouldn't matter because docker IS NOT forwarding that other port, and local connections work fine despite that.
![[MCQA] Kinga Izdebska](../../../data/avatars/users/18949.svg){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
note: it is possible there is some strange way the client deals with NAT and is failing due to a reflection issue. that wouldn't be a bug with the server, and if so, might need to be transferred to the client project instead. i would still classify that as a bug, though, given the total lack of documentation, and the very non-standard behaviour given all the existing apps I serve without issue under my current configuration
(also as a random sidenote, i'm pretty sure the docs don't actually say what protocol the port is using, might want to do that)
me too
for my server
i cant connect using public ip
but when im using vpn from my server, and using local ip to connect, it works fine
so, using this site https://bedrockinfo.com/
i can confirm that the server is on, but cant connect using public ip
Hi Just confirming the same as others. Cannot connect with outside IP only LAN with version 1.16.201 native install not a Docker container.
Hi All. I Just wanted to update this thread. My Server started working in January. The only thing I did differently was re-install my O/S. A friend of mine who is real handy with Wireshark was going to take a look at it so i brought it back online after the O/S re-install, (W10 home on a NUC type device) and before he even started digging into the problem we just tried it and it worked. I wish i could pinpoint exactly why it works now but didnt in December. I literally changed nothing to the setup. my router was already set back in December as well the server was on a USB hard drive that i plugged in and doulble clicked the BDS .exe file and brought it up. The only detail about the operating system that comes to mind is it came with W10 Home OEM 1909 that did a feature update to 20H2 wheras i reinstalled W10 Home 20H2. All the drivers and there are many missing came from Windows Update but i wont worry about no sound on that little machine because my server is working.
I can confirm the same issue on two server (one in my home-lan and one hosted in cloud). Both running as docker containers, but according to Jody Cloutier I don't think this is an Docker issue. Would be nice, if this issue is raised in priority.
I'm having the same issue. Also was running it in a docker container, but I'm having issues running it directly on my machine as well. Connection works fine over LAN but fails using the IP or DNS. Server version 1.16.201.2 and client version 1.16.201 build 5131175. And my server info is shown on that bedrockinfo site too.
Very strange!
I'm having almost the same issue. Native Windows 10 install, BDS 1.16.201.2. I can connect if I'm on my LAN, but trying to connect externally with my public IP fails - with one exception that I discovered earlier today: I have SurfShark VPN installed on my phone and, I have no idea why, but I can connect to my server using the external IP as long as I am connected through my VPN. I was almost out of ideas before I stumbled across the VPN. Unfortunately, this is not an acceptable workaround, as not all of my players pay for a VPN service, and I'm not entirely sure why this works at all, unless some part of the traffic is being blocked by my ISP (Verizon at home and Cricket on my phone). I confirmed that the use of a VPN does enable connections by installing SurfShark on my wife's phone and then attempting to connect from her Android device through the VPN to the public IP of the Windows 10 PC running the server.
I also checked to verify that port forwarding is configured correctly on my router for both Minecraft and XBox Live services. I can also get basic server info from bedrockinfo.com.
Same issue here, started in early January 2021. Running native windows bedrock server 1.16.201.2. I can connect locally but not from outside of my LAN. Ports are forwarding like they should as everything was working fine prior to the update at the end of the year. I even went so far as to create a new server instance on a different computer and a completely different router. Tried different ports too.. nothing.
When running BDS in any virtual/docker environment, make sure the environment is getting the correct time. Once I resolved this some of my connection issues went away.
TL;dr: This issue started for all at the same time the "random ports" started. It also seems to be heavily influenced by port mapping and NATs. It may be that random ports keep being assigned upon connection but it surely seems linked
I think this issue is being sidetracked. I think the issue goes beyond this (and may or may not be related to the tendency of most recent version to assign random port numbers).
It seems in all cases the common thread is double-natting. I have the same issue and I have confirmed it both in Windows and Linux. My servers used to work before the later updates that broke port creation.
I'm running the server behind the ISP Router NAT and then the Eero router NAT.
Public IP > ISP Router full NAT > Eero IP per-port map -> Server IPs
In the same Eero network I have mapped services for Minecraft, Remote Desktop, SSH, Plex, Pihole web server, Sonarr, etc.
Access from the LAN works ok with the individual IP of all.
Access from the ISP router WLAN doesn't work. I can access all the services other than Minecraft in their correct and their mapped ports (respectively).
Access from the WAN works ok with the external public IP for all these services except for Minecraft (same as above), which broke in the same release the "random port number" was introduced.
Like OP, I work in devops and have services and supported networks and servers for all of my long working life. The whole network works but this particular server, which stopped working at the same time it started assigning random port numbers on startup.
So it seems the problem may be directly pointing to port mapping.
Is this being looked at?
Experiencing the exact same problem as described by OP and the rest, and also have a double NAT setup as highlighted seems to be the problem by Eduo above.
Both NATs (ISP Router NAT, then Eero router NAT) are configured properly for port forwarding of port 19132.
But at startup, as noted by the others, a second 'random port' is also assigned:
Server info is successfully seen from WAN when checked via
https://bedrockinfo.com/Server can be connected to successfully from within LAN, but from WAN, searching for the IP/port combo from within Minecraft Bedrock shows no ping success, no server-name found, and "unable to connect to world".
Please help, Mojang!
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Is this still an issue in the latest version? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Anyone watching able to confirm this as an issue? I'm 99.9999% sure they didn't fix this, but I also enabled local reflection on my router/dns to avoid such issues, and I don't particularly feel like changing that to confirm this :sweat_smile:
It's working! Running a 1.17 image provided by marctv via docker on synology. I can now connect locally and remotely again.
The same issue with 1.17.11.01. I have ASUS RT-AC66U with enabled port forwarding (I have few more services on the same machine where Minecraft server is dockerized and all of them are working). Random ports in Minecraft are also present:
Server accessible from within LAN but not accessible from WAN with obvious "Unable to connect to world". Please help!
Hi
Does this issue still occur after updating to 1.18.2?
This ticket will automatically reopen when you reply.
Bedrock 1.18.2.03 doesn't fix this for me.
If I port forward 19132 externally to one of my docker containers' port 19132 then both iOS and Windows clients can ping the server and connect successfully.
However, any other external port number causes all clients to fail to ping or connect.
I have four dockerized Bedrock servers using macvlan networking resulting in separate LAN IP addresses so they can all expose the default port and be discovered by LAN-connected clients. Only mapping UDP port 19132 specifically through the router will result in a successful external client connection to any one of them (one at a time depending on the forwarding target IP).
Hi
Does this issue still occur after updating BDS to 1.18.11?
This ticket will automatically reopen when you reply.
No change at all from my point of view. My earlier comment still holds.
Was there a code change in this area in 1.18.11 that was expected to change this behaviour?
Nope, they just close/reopen stuff seemingly every release due to some internal policy probably to try and prune tickets by "what's getting attention and what we can ignore". I'd be more critical if I didn't see a bunch of "help me understand what servers are and how to operate them" tickets along with a bunch of "I can't use the game client correctly" noise in here, but they do need a way to get through that cruft.
same issue;
multiple physical servers with different IP addresses
Issue still occurs with the most current version.
however since I also operate a site-to-site VPN between my house & my in-laws; at my in-laws house my home operated server appears in the Friends Tab under LAN Games on my in-law's PC instance of Minecraft Bedrock.
link to my Bug Report:
BDS-17011Hi
Does it still occur? Can you get servers running and connecting outside of docker?
This ticket will automatically reopen when you reply.