Started server on Windows 10:
e:\Minecraft>bedrock_server.exe
NO LOG FILE! - setting up server logging...
[2020-05-30 16:51:25 INFO] Starting Server
[2020-05-30 16:51:25 INFO] Version 1.14.60.5
[2020-05-30 16:51:25 INFO] Session ID 3af194fd-5a70-4a96-808a-9b92c43615cd
[2020-05-30 16:51:25 INFO] Level Name: Bedrock level
[2020-05-30 16:51:25 INFO] Game mode: 0 Survival
[2020-05-30 16:51:25 INFO] Difficulty: 1 EASY
[2020-05-30 16:51:26 INFO] opening worlds/Bedrock level/db
[2020-05-30 16:51:28 INFO] IPv4 supported, port: 19132
[2020-05-30 16:51:28 INFO] IPv6 supported, port: 19133
[2020-05-30 16:51:28 INFO] IPv4 supported, port: 60578
[2020-05-30 16:51:28 INFO] IPv6 supported, port: 60579
[2020-05-30 16:51:29 INFO] Server started.
Server is NOT listening on any ports, hence clients cannot connect to it.
Nestat command does not show any of the ports above in the listening state (for either TCP or UDP).
nestat -b (on windows) does not show any ports opened by bedrock_server.exe
Windows firewall is disabled.
Cannot connect to the any of the ports above from either localmachine or remote machine (but telnet'ing on the port above). Game on iOS cannot connect to the server as well
The same behavior when Ubuntu's version is installed on Ubuntu 20.04
Comments 8
Is the command prompt/powershell window you are running from an administrative prompt?
Almost every instance of being unable to connect generally comes back to a technical issue rather than a bug. Please note some port checking tools (such as telnet) can cause a specific thread to crash preventing connection so make sure anything like that is disabled.
Connecting locally requires a workaround that is detailed in the readme.
Other causes can be time sync.
Running in non admin prompt. Why is the admin prompt required?
Per my bug description telnet to ports does not work from remote machine. Netstat does not snow ports in listening state.
Running in non admin prompt. Why is the admin prompt required?
Per my bug description telnet to ports does not work from remote machine. Netstat does not snow ports in listening state.
Running in admin prompt solved problem. Nowhere in the how to file it states That exe must run from elevated prompt.
please update instructions to capture this fact.
Running in admin prompt solved problem. Nowhere in the how to file it states That exe must run from elevated prompt.
please update instructions to capture this fact.
Is the command prompt/powershell window you are running from an administrative prompt?
Almost every instance of being unable to connect generally comes back to a technical issue rather than a bug. Please note some port checking tools (such as telnet) can cause a specific thread to crash preventing connection so make sure anything like that is disabled.
Connecting locally requires a workaround that is detailed in the readme.
Other causes can be time sync.