ProxyPingEvent error about realip HOT 9 CLOSED

I can confirm this is an issue, my logs keep getting spammed with it.

from realip.

I have the same

from realip.

Can your players still log in? I've tested with this:

• TCPShield plugin 2.6.0
• Velocity 3.1.2-172
• Plugins: ViaBackward, ViaVersion, Geyser-Velocity
  The errors did indeed show but I have no issue logging in.

Another test version I have is:

• TCPShield plugin 2.6.0
• Velocity 3.1.2-161
• Plugins: ViaBackward, ViaVersion, Geyser-Velocity
  No errors were shown. You might need to downgrade your Velocity build or use proxy-protocol instead.

from realip.

Yes. Velocity builds can't be downgraded at the moment, it is critical you stay on latest due to mojang's insane protocol changes re:chat

from realip.

Already made a note with our dev 2 days ago*. At the moment can you switch to proxy-protocol instead? Instructions can be found here:
https://docs.tcpshield.com/commonly-asked-questions

from realip.

The documentation in TCPShield didn't help me... And when I turn on the proxy, I write constantly: "Disconnection"

from realip.

The documentation in TCPShield didn't help me... And when I turn on the proxy, I write constantly: "Disconnection"

You have to do all of these steps:

• Remove TCPShield plugin (make sure the .jar is gone)
• Enable proxy-protocol (or haproxy-protocol if you are using Velocity) in your proxy's config.
• Enable proxy-protocol in your backend set on the TCPShield Web panel.

And obviously direct login using IPv4 won't work because it's expecting proxy connections

from realip.

@Xemorr I've looked through the errors here and you seem to be using a very old version of the plugin, could you come to Discord so we can assist you further? https://discord.gg/tcpshield

from realip.

Nevermind, I'm stupid. Fixed version here: https://github.com/TCPShield/RealIP/releases/tag/2.6.1

from realip.