Uploaded image for project: 'Bedrock Dedicated Server'
  1. Bedrock Dedicated Server
  2. BDS-11667

"Unable to connect to world" from Windows 10 Edition and Android Edition

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • None
    • 1.16.201.03 Hotfix
    • None
    • Unconfirmed

      According to this Minecraft Wiki article, the Windows 10 Edition should be able to connect to a Bedrock server. So I set one up on my dedicated server using the official software from the Minecraft website and used Nmap to verify the port is open:

      map scan report for my.domain (my.public.ip.address)
      Host is up.
      rDNS record for my.public.ip.address: my.domain
      PORT STATE SERVICE
      19132/udp open|filtered unknown
      Nmap done: 1 IP address (1 host up) scanned in 2.48 seconds
      

      And when I run that, I get this in the Bedrock server console:

      ATTENTION! Received EMPTY UDP packet - potential UDP ports scanning.
      ATTENTION! Received EMPTY UDP packet - potential UDP ports scanning. 
      

      So the server does appear to be running correctly.

       

      But when trying to connect from the Windows 10 Edition or the Android Edition, I just get an "Unable to connect to world" error message and nothing appears in the server console.

       

      EDIT1:
      I tried running the Bedrock server locally too in WSL2, ran the PowerShell command to allow loopback connections from UWP apps and I can connect to that as it appears in the LAN section, it also seems to work when typing the IP address of the WSL2 instance in server section.

      EDIT2:
      Never mind, this issue can be closed. 
      Summary that could help others:

      • A good ole Windows-style "turn it off and on again" worked for the Windows 10 Edition. I was then able to connect to the remote server.
      • I figured I wasn't able to connect on my Android device because I was logged into the same account on the Windows 10 Edition.
      • I have both IPv4 and IPv6 addresses set up with my DNS provider, however, my pfSense software router only routes IPv4 to the containers (which includes the Bedrock server), my home broadband supports IPv6 so I'm guessing IPv6 took precedence leading to some of the connection failures until I used a specific subdomain for the IPv4 address only. 

            Unassigned Unassigned
            PairedPrototype PairedPrototype
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: