[BDS-85] No-one can join my server (Bedrock Server Software Alpha) Created: 20/Sep/18  Updated: 08/Aug/20  Resolved: 08/Aug/20

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.6.1.0
Fix Version/s: None

Type: Bug
Reporter: Ruben Adema Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 10
Labels: awaiting-response

Confirmation Status: Unconfirmed

 Description   

I can't join my server, I've started it up, added me and my friends to the whitelist and entered my ip but it just says "Locating server" and if I try to join it says "Unable to connect to world"



 Comments   
Comment by IonicEcko [ 08/Aug/20 ]

Thank you all for your participation on this report.

This report has deviated somewhat from a bug report into more of a tech support thread and unfortunately the bug tracker isn't equipped for that kind of discussion. As such I'm going to close this specific report off as cannot reproduce. I've not been able to reproduce connection issues across numerous VPS providers and firewall configurations across both supported operating systems (Windows 10/Server 2019 and Ubuntu).

If you believe there to be an outstanding bug related to connectivity that is reliably reproduced please feel free to raise a new report with those details.

Please don't forget to check the technical pieces first though, there are amazing people over at the Community Support Discord that are available to help if you need it. Before reporting a bug please check:

  • Make sure you are using a supported operating system (Windows 10 1709 or newer, WIndows Server 2019 (with GUI) or Ubuntu 18.04 or newer).
  • Ensure your system time is correct (this one seems silly but its been the cause of many of the "can't connect" reports, including many where connectivity works initially but fails soon after).
  • That your firewall and any port forwarding is configured correctly on both your server and your router and that your ISP allows port forwarding. Many ISP's use CGNAT or block ports, this will prevent outside access no matter the config on your router.
  • If trying to connect to a BDS instance on the same PC you are playing on, check the Windows section of the bedrock_server_how_to.html file and make sure you have run the CheckNetIsolation commands.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

Comment by [Bot] Arisa [ 29/Jun/20 ]

An attachment with a disallowed file extension has been removed from this ticket.

Executable files and documents are not allowed as attachments.
Please attach crash reports, log files and screenshots as they are instead of pasting them into a document.
– I am a bot. This action was performed automagically! Please report any issues in Discord or Reddit

Comment by Dan Martin [ 29/Jun/20 ]

IF you are setting up local host 127.0.0.1 you may need to open the read me file and paste that command in a administrator cmd prompt,  otherwise you will need to setup port forwarding on your router,  it nomaly located at http://192.168.1.1 admin password  for Username and password , find port forwarding set the port to default server and use your computers DHCP address 192.168.1.? what your computer local ip is set to... Also  i would use TCP/UDP and there is two ports for each you will need to set. 92??? and 52??? .

Comment by Vanegas W [ 19/Apr/20 ]

Hey, dude, I have a problem with bedrock server software, I can't join my server, I've started it up. I entered my ip but it just says "Locating server" and if I try to join it says "Unable to connect to world". Please,man, tell me how can I solve this error?

Comment by Gordon Henderson [ 02/Apr/20 ]

Joel, can you share a little more on how you got it to work?  I'm trying to launch the server on a Google Compute Engine and can't seem to connect to the server after setting firewall rules, etc.  Any help would be appreciated.

Comment by Joel Greenwood [ 01/Apr/20 ]

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

Comment by IonicEcko [ 29/Mar/20 ]

Hi Joel,

There's so much that could be wrong with your setup and unfortunately this isn't really the place to troubleshoot it. This is for bug reports as opposed to tech support issues. You may find someone from the community is willing to help over at the Community Support Discord.

One thing I will mention though is that you keep mentioning Java, please note that the two are different in a number of ways, for example:

  1. Minecraft Bedrock uses UDP unlike Java which uses TCP, please make sure your port forwarding and firewall rules are set up for UDP.
  2. The Bedrock_Server executable can't be run without ALL supporting files. You need the entire zip file that is downloaded. It isn't like Java where the EXE will download missing pieces.

Ionic

Comment by Joel Greenwood [ 29/Mar/20 ]

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!

 

Comment by Joel Greenwood [ 26/Mar/20 ]

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.

 

Comment by Dale Monks [ 05/Mar/20 ]

I always need to change the port from the defaut 19132. Both 19131 & 19133 work fine! Ensure you have port forwarding and firewall exxceptions setup correctly. 

Comment by IonicEcko [ 04/Mar/20 ]

Hi Ruben,

Did you get this sorted?

Ionic

Comment by João Vitor Vargas [ 22/Sep/19 ]

Fix: Disable "Block ping" on firewall settings

Comment by Jonny [ 12/Sep/19 ]

I also have this issue with 1.12.1.1. Tried ports 19132, 52599, 50000 - nothing seems to work. Other ports for other services on the same machine all work. Installed on Windows Server 2016.

Can connect over LAN, not WAN.

Comment by techy 804 [ 10/Jun/19 ]

I had the same issue until I set the port to 50000 instead of 19132

Comment by Thomas Parks [ 01/Jun/19 ]

I tried as well. Works fine with clients ok the same local network. Does not work outside the net.

Comment by Devin Illy [ 15/Mar/19 ]

Same problem, I actually have 2 Java edition servers (one modded[25565] and one vanilla[25566]) that both work fine. I put the bedrock server on port 25567. Neither of the other servers were running in the background. The server window said the server started correctly, so I typed in my IP (the same one that works for both Java edition servers) and 25567 in the port box (I did this on an iPad to avoid the same machine loop-back whatever) but cannot connect.

Comment by Ron Craig [ 02/Nov/18 ]

Hi Scott,

by "New server version" are you talking about version 1.7.0.13? I've tried that with no luck. Did you do anything special to get it to work? 

 

Thanks,

 

Comment by Ron Craig [ 20/Oct/18 ]

guess we wait for the next patch/update. Going back to the Java version until then. 

Comment by Dale Monks [ 19/Oct/18 ]

Same issue here. Was working fine before the upgrade. Downloaded and ran latest build with a fresh world. All users can join added server using IP or host name on WiFi and via LAN, but not externally. Running server 2016 with correct ports open and other applications running and connecting successfully. 

Comment by Daniel [ 18/Oct/18 ]

I'm having the same problem as Ron. Ports forwarded correctly, even tried DMZ. Turned off both the router and computer's firewall, and still the port comes up as not being open when tested. The same computer hosts StarBound just fine, I can even host it using the same ports (not at the same time obviously) and it works just fine, so it's not an ISP blocking issue either.

Comment by Ron Craig [ 13/Oct/18 ]

Let me ask this. Has any one successfully had people from outside their network connect? If so can you tell us a little about your setup? 

Comment by Scott Rowley [ 12/Oct/18 ]

I am also having the issue with remote users connecting to the server.  Server status on the LAN is fine and users can connect.  External users can't even get server status to spite having the port forwarding rules set to allow tcp/udp 19132.  I also set ufw allow rules on the ubuntu firewall.  So it looks like this is an issue with both windows and linux.

UPDATE

New server version fixed connectivity problems for me with external users...They can now connect remotely.

Comment by Ron Craig [ 10/Oct/18 ]

I am having similar issues with remote players trying to connect to the server. I am running the server on a Dell T330 running server 2016. I have opened the default ports 19132 and 19133 on both my router and firewall. Minecraft Server properties file is configured to use these ports. I also have a team speak server running on the machine.

No issues connecting to the Minecraft server from a windows 10 machine on the network. However no one outside the network can connect. I’ve tried using different ports. I even tried the loop back exception for good measure. I’m pretty sure everything network wise is configured correctly because we have no issues using the team speak server.

Any help and/or advice on this issue would be greatly appreciated.

Comment by Cory Parker [ 22/Sep/18 ]

Ruben: Have you port forwarded through your router and made sure to set up your pc as a static ip? Have you tried connecting locally from another computer/device on the same network?

 

Comment by KillerbeeNL [ 21/Sep/18 ]

Inside the Zip there is a file: bedrock_server_how_to.html. It describes when connecting to localhost or 127.0.0.1 that you might need to allow a exemption.

"On some systems, when you wish to connect to the server using a client running on the same machine as the server is running on, you will need to exempt the Minecraft client from UWP loopback restrictions:

CheckNetIsolation.exe LoopbackExempt –a –p=S-1-15-2-1958404141-86561845-1752920682-3514627264-368642714-62675701-733520436"

Comment by Peter Hedberg [ 20/Sep/18 ]

Same here. I've tried with the default server.properties and connect to localhost or 127.0.0.1.

Generated at Sat Jan 11 07:12:49 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.