Skip to main content

Investigate “A plugin tried to cancel a signed chat message.”

Applies to: Velocity signed-chat cancellation paths described for Minecraft 1.19.1-era and newer protocol behaviour; bridge/plugin compatibility is release-specific.
Documentation checked .

A plugin tried to cancel a signed chat message. is a documented Velocity warning associated with disconnecting a player after a proxy plugin tries to cancel signed chat. The connection may work until someone sends a message or triggers a moderation rule. This is a chat-processing compatibility problem, not evidence that the player supplied an invalid password.

Reproduce the narrow symptom safely

Record the client version, Velocity build, backend software/version and relevant chat or moderation plugin releases. Note whether the disconnect happens on every message, only blocked phrases or only one backend. Preserve the proxy log around the event and the backend log for the same time.

Use a controlled staff test account and a harmless test rule rather than publishing abusive text or removing moderation for the whole community. Keep logs private where they contain player messages or personal information. A client screenshot of a disconnect is useful context, but the proxy's original warning identifies this failure more precisely.

Identify the component trying to cancel

Check which proxy plugins inspect, rewrite or block chat and commands. A plugin configured to cancel a message can trigger a different path from one that merely observes it. Compare recent configuration or plugin updates with the first occurrence of the problem.

Minecraft's signed-chat changes began with 1.19.1-era behaviour described by Velocity's FAQ. Signing is about message authenticity; it does not make chat confidential. Current server releases and plugins may have different handling, so verify the exact compatibility matrix instead of treating an old workaround as universal for 1.21.11 or 26.x.

If possible, isolate the suspect combination on a separate network copy with production integrations disabled. Do not broadly unload protection plugins on a public server. A plugin name elsewhere in the log is a clue, not proof: compare the specific rule or action that triggers cancellation.

Check the supported integration path

Velocity's FAQ points to SignedVelocity for coordinating certain proxy message/command changes with the backend. If that approach is appropriate for your versions, read its current author's instructions and release compatibility first. It is not enough to upload one arbitrary JAR bearing that project name.

The project's documented deployment uses the proxy component and the appropriate component on every relevant backend. Download the correct platform artifacts from the official project, preserve previous plugin state and avoid duplicate releases. A mixed or incomplete installation can leave the symptom on only some destinations. If your version or backend is not supported, ask the plugin maintainers for a supported alternative.

Verify behaviour rather than only startup

Apply an agreed plugin/configuration correction in a planned maintenance window and start the affected components normally. Test an ordinary permitted message and the harmless moderation test case. Confirm both the expected moderation result and that the player remains connected. Repeat after switching between each backend that uses the chat path.

Inspect fresh logs for the original warning and any replacement error. A green plugin entry or disappearance of one warning is not sufficient if messages are now duplicated, blocked incorrectly or bypassing moderation. Keep the test results with the exact versions used.

Recover without weakening authentication

Restore the previous compatible plugin/configuration set if the trial fails, accounting for any data migrations. Do not disable public account authentication, remove forwarding verification or blindly disable secure-profile checks to suppress the symptom. Send maintainers a minimal version list, redacted log interval and reproducible harmless rule. World files do not need to be deleted or restored for this chat-processing investigation.

Official references

Velocity signed-chat cancellation warning. SignedVelocity author installation instructions.

No comments to display