search

Doclic / NoEncryption

Removes signatures from Minecraft chat messages
GNU General Public License v3.0
224 stars 18 forks source link

Velocity kicking players for not having a signed message #36

Closed Impactic48 closed 1 year ago

Impactic48 commented 1 year ago

Sometimes when a player talks in chat they will get kicked with the error message listed in the logs below.

Version: Purpur 1.19.2 Video: https://youtu.be/zLOxXsJ2Y8I Log file: https://mclo.gs/J9ZT0Ye

V1nc3ntWasTaken commented 1 year ago

I will do some further research to see if this is an avoidable problem for Velocity.

V1nc3ntWasTaken commented 1 year ago

If possible, can you please describe a way to recreate this, and send me info such as plugin version, server version, velocity version, server type, etc.

Impactic48 commented 1 year ago

If possible, can you please describe a way to recreate this, and send me info such as plugin version, server version, velocity version, server type, etc.

Server Version: Purpur 1.19.2 Velocity Version: 3.20-SNAPSHOT

Plugins on proxy and backend: LiteBans (LiteBans is causing this issue) Plugins on backend: NoEncryption 1.19.2

How to recreate:

  1. Mute player
  2. Get player to send a message in chat
  3. It should kick player with the message shown

This may just be a LiteBans issue tbh,

V1nc3ntWasTaken commented 1 year ago

So, upon further testing, I have tried this with LiteBans tied over a database on a proxy running Velocity Build 229 and on a server running Purpur Build 1858 for 1.19.2 and it looks like that this is a LiteBans problem.

The console message A plugin tried to cancel a signed chat message... and player disconnect message A proxy plugin caused an illegal protocol state.... kinda debunk this issue in a way, saying that a proxy plugin is the issue. On the server console side of things, I am only provided with V1nc3ntWasTaken lost connection: Disconnected which indicates that a disconnect status was sent to the server, and not a Lost Connection status. I tested this with and without NoEncryption v4.1 for 1.19.2 on the backend.

I went ahead and made an issue on the LiteBans GitLab which can be found here.

V1nc3ntWasTaken commented 1 year ago

So it looks like the issue created on the LiteBans GitLab was closed, but provided a possible solution to your problem.

Installing LiteBans under the backend servers - if you still need LiteBans on the proxy instance, you can disable mutes in the configuration to have mutes enforced by the backend instances instead of Velocity.