Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-180876

Server connection issue: When connecting to Snapshot 20w17a server, connection will be closed if any server in server list cannot be connected to

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • 20w17a
    • None
    • Unconfirmed
    • (Unassigned)

      Hello team,

      I have been having an issue connecting to a friend's snapshot server, and we initially thought that my connection was somehow getting dropped through a node between myself and the server.  Considering I am in US West and the server is in Germany, this made sense.  I tried connecting through a VPN and was getting the same issue.  After some debugging, we found that the issue is that the game is somehow trying to connect to other servers in my server list, and since they're hosted on older versions, the connection fails, and my connection to the snapshot server is forcibly closed 10-30 seconds after I connect.  This was confirmed by the debug console where it was throwing the error `Can't ping [IP 1]: Timed out` while I was attempting to connect to [IP 2].  After clearing my server list, the issue was resolved.

      This is not happening on 1.15.  I am able to successfully connect to 1.15 servers with the snapshot server in the list 100% of the time.

      Attached is a screenshot of the error I was getting when my connection to the server was closed.

      Steps to duplicate:

      1. Launch Minecraft in Snapshot 20w17a (This was happening in 20w16 as well).
      2. In the server list, add one or more working servers which are running an incompatible version to the snapshot.  I also had the snapshot server in the list, but direct connection to the IP was yielding the same results before clearing the server list.
      3. Connect to the snapshot server.  Connecting either through the server list or by direct connect should produce the bug.
      4. Wait for up to a minute to get the 'connection forcibly closed' error.  You may need relog in order to produce the bug, as sometimes I did get a successful, albeit a laggy, connection.

      Workaround:

      Remove all incompatible servers from the server list.  After this, there should be no connection issues to the snapshot server.

      Thanks.

            Unassigned Unassigned
            mdog95 Morgan West
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: