-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
DecoderException - [Proxy] Lost connection to server #1883
Comments
Even deleting the whole world on your hub server didn't do the trick? Try emoving skins restorer. |
Removing SkinsRestorer did not change anything. |
Please remove all plugins from both server and bungee. This looks almost certainly plugin induced. |
Removed all plugins from bungee, nothing changed. Now trying to remove the plugins from the server. |
Did you manage to fix it? |
Updated Bungeecord and this still happens: http://pastebin.com/g7XKb2F2 |
Even after removing all spigot plugins? |
Now removed all the plugins and started testing. |
It's definitely an outdated or bad written spigot plugin. |
With no plugins on the spigot server, this error comes up in the console of the spigot fallback server:
The player gets this message https://i.gyazo.com/63f01379a96e888964565bd6dbef7793.png Also tried to delete all the worlds, same error. This does NOT happen to all the players, but just to a few, and when it happens all the players online in the server get kicked with the same error. |
Error: http://pastebin.com/sC0rEZ6K
Plugins on bungeecord:
Latest RedisBungee, Latest BungeeAuthMeBridge, Latest SkinsRestorer
Bungee version #1158 downloaded from the official jenkins.
Only happens with certain players.
Deleting all player data from the fallback server (essentials, world .dat files...) did not do any difference.
Using no plugins on the fallback server did not do any difference.
When he tries to connect with 1.9 it just throws the proxy connection lost error, while on 1.8 it throws the error in the pastebin.
When he joins the server he gets instantly kicked and all the players in the server are kicked for the same exact reason.
Tested and reproduced on different computers with the same account and the same result shows up, so it is indeed a server-related problem and not client-side.
The text was updated successfully, but these errors were encountered: