-
-
Notifications
You must be signed in to change notification settings - Fork 639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpectedly disconnected from remote server #1251
Comments
You are using an old version, can you try the latest build? |
This time, the error on velocity is gone (1h40m uptime), however, the glitched backend message stays, since the user never actually joined it. Velocity 362, no resource pack Backend message:
Velocity logs:
|
Update: One dude actually managed to trigger the error even on the Velocity 362 (no resource pack). Backend (hub) logs:
Velocity logs:
|
Can you try the latest version? |
Unfortunately, the bug still happens even on the latest velocity version. Backend (hub) logs:
Velocity logs:
|
Unknown if this related but when I try and join a server while already having been on a server before I now get a "An internal error occurred in your connection." This happening during the Config Phase as I never see the server before disconnected and am in the dirt screen for awhile. There are no errors in the logs. |
@4drian3d This issue is still present in latest velocity. |
Still persists in 8f4adb1. |
I have ran build 358 (the build before 359 which in the original post was said to have this issue) for a few months. During that, I never saw this issue. |
Still an issue on b428
|
So the issue is player connecting to 2 backend at the same time? If so how could that even occur? Also shouldn't velocity drop everything and only handle latest connection? Trying to think of what end result of 2 player connect to 2 backends would look like... |
Have a snippet or something of the short that indicates what reversion fixes the issue? |
Sure #1459 |
@4drian3d please remove status awaiting response, we can provide all you need |
I have the same problem on Velocity 3.4.0-SNAPSHOT (git-cefa3b27-b450). Many cases like this. |
Similar issue |
There is also the problem that server is switched, the client has to re-enter the config phase, but sometimes just doesn't respond with a FinishedUpdatePacket. (and it might be a Minecraft client bug, because I tried everything, but because of the nature of the bug I couldn't get a packet log from the clients view) If the server has the same data packs, features, etc. enabled the client doesn't have to enter the config phase, which improves load times and also just removes this point of error (and the unsecure chat popup also doesn't appear after every switch) At least that completely solved the issue for our server. |
We have random disconnects like this without any datapacks, occurring on server switch. |
You could try #1477 |
Sometimes, when a player has a weird connection, they are kicked to the fallback server without properly joining it, which causes an error on proxy, as well as some random message on the backend server.
Upon asking, I was told that this error is caused by the client being stuck in the configuration phase, because the proxy did not receive any packets from the client.
Happened on Velocity 359 with no resource pack.
Backend message:
Velocity error:
The text was updated successfully, but these errors were encountered: