-
Notifications
You must be signed in to change notification settings - Fork 39
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
Server crash with pipeline not initialized #221
Comments
Exactly same spamming happened to us, we have discovered with our host that this is related to an exploit involving handshakes. Basically attacker is sending multiple malformed handshakes, server doesn't crash due to the host filtering most of the attack but there is huge console spam |
I just have a lot of bot attacks, and even the lowest one was crashing the server. the issue was with protocolozy. The issue is that protocolize fails a packet on PLAYER PING, each time a player pings the server it executes a packet event and that can saturate de cpu. here is the output of what was happening. |
Hey, what plugins do you have installed on Velocity? This issue currently only occurs when having Geyser installed, which is currently incompatible with protocolize. |
From the error beside, Protocolize is doing everything right here. It is it's job to process incoming events. If you want to mitigate dos attacks, you should consider adding a TCPShield proxy in front or use dedicated anti DDoS hard- and software like SteelShield for example. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Not sure how this can be reproduced
Expected behavior
Server doesnt crash
Screenshots
https://pastebin.com/eRmJZyHU
Proxy environment
Velocity latest version
Minecraft versions used
Only proxy
The text was updated successfully, but these errors were encountered: