I am having the same problem. I can connect from the bedrock server on LAN but not the WAN. I can see that the server is opening ports 19132 and 19131; however, they are not listed as "LISTEN" like the ports are for my java server. I'll paste the output of:
sudo lsof -i -P -n
so you can see what I'm seeing.
bedrock_s 12129 dad 10u IPv4 1289832 0t0 UDP *:19132
bedrock_s 12129 dad 11u IPv6 1289833 0t0 UDP *:19133
bedrock_s 12129 dad 12u IPv4 1289853 0t0 UDP *:44445
bedrock_s 12129 dad 13u IPv6 1289854 0t0 UDP *:57512
I have been able to open ports and forward through the router without any trouble. It would appear that the bedrock server is opening the udp ports differently than the tcp ports for the java server.
Thank you for getting back to me. I understand there are a lot of things that could be wrong! I understand that Bedrock uses UDP and java uses TCP. I was able to resolve my issue but I'm still trying to track down the details so I can help other people with the same problem. I'm running the server on Ubuntu 18.04. What fixed it was running the server under a dedicated user who's home directory is /opt/minecraft
This points to some sort of permissions problem (the other user was in the normal path: /home/user/). I have no idea why I would be able to run a LAN server from the /home/ path with the WAN not working while being able to run a server on LAN and WAN if the home directory was in the /opt/ path. Absolutely nowhere in google or this board was I able to find help pointing to that as a potential problem. This is clearly nothing to do with the program - so it's "my fault." But my guess is there are quite a few people that are running into the same mysterious problem. I consider this request to be solved and closed but if there's anyway to suggest this as a fix or put it in a troubleshooting section I think that could help others.
I am having the same problem. I can connect from the bedrock server on LAN but not the WAN. I can see that the server is opening ports 19132 and 19131; however, they are not listed as "LISTEN" like the ports are for my java server. I'll paste the output of:
sudo lsof -i -P -n
so you can see what I'm seeing.
bedrock_s 12129 dad 10u IPv4 1289832 0t0 UDP *:19132
bedrock_s 12129 dad 11u IPv6 1289833 0t0 UDP *:19133
bedrock_s 12129 dad 12u IPv4 1289853 0t0 UDP *:44445
bedrock_s 12129 dad 13u IPv6 1289854 0t0 UDP *:57512
vs:
java 832 minecraft 59u IPv6 33870 0t0 TCP *:25565 (LISTEN)
java 832 minecraft 68u IPv6 30391 0t0 TCP *:25575 (LISTEN)
I have been able to open ports and forward through the router without any trouble. It would appear that the bedrock server is opening the udp ports differently than the tcp ports for the java server.
Any help is greatly appreciated.
I've now tried the DMZ. The java minecraft server works great but the bedrock server is still inaccessible from the outside world (WAN) while working fine on the LAN. When I place the server in the DMZ then a NAT reporting tools ( https://blog.adityapatawari.com/2014/09/types-of-nat-and-how-to-determine-nat.html ) says:
This is Address Restricted Cone NAT
When I'm not in the DMZ but forwarding ports through the router the NAT tool says:
This is Port Restricted Cone NAT.
Do these clues help diagnose what's going on? I really want to get this server running!
Thank you for getting back to me. I understand there are a lot of things that could be wrong! I understand that Bedrock uses UDP and java uses TCP. I was able to resolve my issue but I'm still trying to track down the details so I can help other people with the same problem. I'm running the server on Ubuntu 18.04. What fixed it was running the server under a dedicated user who's home directory is /opt/minecraft
This points to some sort of permissions problem (the other user was in the normal path: /home/user/). I have no idea why I would be able to run a LAN server from the /home/ path with the WAN not working while being able to run a server on LAN and WAN if the home directory was in the /opt/ path. Absolutely nowhere in google or this board was I able to find help pointing to that as a potential problem. This is clearly nothing to do with the program - so it's "my fault." But my guess is there are quite a few people that are running into the same mysterious problem. I consider this request to be solved and closed but if there's anyway to suggest this as a fix or put it in a troubleshooting section I think that could help others.
Best,
Joel