You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I setup a VM running ubuntu 20.x. I installed Minecraft Bedrock Server on it, configured it, and started the server. I am running the "phantom-linux-x64" instance of phantom on a local debian machine. I modified firewall rules on the networking devices, my server, and on my local machine. Once my firewall rules were active my PS4 immediately saw the phantom proxy and listed the correct Server Name. The PS4 shows: Dedicated Server, my server name, and version 1.16.40 as available. When I select this from within the PS4 it changes screens then eventually gives the error:
Unable to connect to world
OK
The only option I can select is the "OK" button.
I know the phantom instance is able to see my server because it is listing the correct Server Name within the PS4. From within my PS4 I can also see the correct number of possible players on my server, and it shows a green circle next to the LAN icon.
I know my Minecraft Bedrock Server is working because I can use an Android application as the proxy and I am able to connect to my server and play from my PS4. I do not want to use my Android device every time I want to connect to my server. I would prefer to use Phantom as I can leave it running, not add more garbage to my Android device(s), connect to multiple servers (my eventual plan is to host several minecraft servers), and I would just rather use Phantom.
When I use the -debug option when executing phantom it does not seem to provide any obvious insights.
Any ideas related to fixing this would be appreciated.
The text was updated successfully, but these errors were encountered:
TimesEnemy
changed the title
Unable to connect to world - Debian server Debian client/proxy
Unable to connect to world - Ubuntu server Debian client/proxy
Nov 8, 2020
TimesEnemy
changed the title
Unable to connect to world - Ubuntu server Debian client/proxy
Unable to connect to world - Ubuntu server Debian client/proxy PS4
Nov 8, 2020
I setup a VM running ubuntu 20.x. I installed Minecraft Bedrock Server on it, configured it, and started the server. I am running the "phantom-linux-x64" instance of phantom on a local debian machine. I modified firewall rules on the networking devices, my server, and on my local machine. Once my firewall rules were active my PS4 immediately saw the phantom proxy and listed the correct Server Name. The PS4 shows: Dedicated Server, my server name, and version 1.16.40 as available. When I select this from within the PS4 it changes screens then eventually gives the error:
The only option I can select is the "OK" button.
I know the phantom instance is able to see my server because it is listing the correct Server Name within the PS4. From within my PS4 I can also see the correct number of possible players on my server, and it shows a green circle next to the LAN icon.
I know my Minecraft Bedrock Server is working because I can use an Android application as the proxy and I am able to connect to my server and play from my PS4. I do not want to use my Android device every time I want to connect to my server. I would prefer to use Phantom as I can leave it running, not add more garbage to my Android device(s), connect to multiple servers (my eventual plan is to host several minecraft servers), and I would just rather use Phantom.
When I use the
-debug
option when executing phantom it does not seem to provide any obvious insights.Any ideas related to fixing this would be appreciated.
Possibly related threads: https://github.com/jhead/phantom/issues/63, https://github.com/jhead/phantom/issues/71, https://github.com/jhead/phantom/issues/73, https://github.com/jhead/phantom/issues/117#issuecomment-679101818, https://github.com/jhead/phantom/issues/105#issuecomment-658408334, https://github.com/jhead/phantom/issues/104
The text was updated successfully, but these errors were encountered: