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

Unable to Connect to World

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • 1.8.0.24
    • None
    • Setup Azure VM running Windows Server 2016
      Running bedrock_server.exe version 1.8.0.24

      Tested on Clients

      Win 10
      iPhone

      both clients tested when signed in xbox live account

      Using Static IP (on server)
      Added new Inbound port rule to allow Any Source, Destination Any for port ranges 19132-19133 on Any Protocol.
      fresh copy of the VM
      Installed https://aka.ms/vs/15/release/vc_redist.x64.exe to get some c++ runtimes working
      ran bedrock_server.exe both clients (win10, iphone) failed
      disabled server 2016 firewall and tried again on both clients
      still get Unable to Connect to World

      Everything else is default (on the servers)

      Azure VM is pretty much default Windows Server 2016 image with the only real non-standard things being, I allowed RDP and allowed 19132-19133

      It tested before on Azure with version 1.6.1.0 and it worked then (server 2012)
      I still have the server (the clients are updated and it won't work on 2012 because of chakra.dll)

      One thing different in the bedrock console window
      In 1.6.1.0 the status goes
      IPv4 supported, port: 19132
      IPv6 supported, port: 19133
      Listening on IPv6 port: 19133
      Listening on IPv6 port: 19132

      But on 1.8.0.24
      IPv4 supported, port: 19132
      IPv6 supported, port: 19133
      Server started

      Not sure if the console got changed to be "Server Started" instead of "Listening on x port: y" or if 1.8.0.24 should say Listening on port 19132?

            Unassigned Unassigned
            ondrelogin Andre
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: