mojira.dev
BDS-10608

Can't connect from non-local networks (outside of LAN)

Resolved
Awaiting Response
12

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. 

Comments 42

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)

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

  • using screen to start the server, and default server.properties

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

me too

for my server

  • using screen to start the server, and default server.properties

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. 
 

32 more comments

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-17011

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-17011

Hi

Does it still occur? Can you get servers running and connecting outside of docker?

This ticket will automatically reopen when you reply.

Hi

Does it still occur? Can you get servers running and connecting outside of docker?

This ticket will automatically reopen when you reply.

Tareef Dedhar

(Unassigned)

Community Consensus

Retrieved