Direct answer

Chat signature or validation failures should first be diagnosed as a client/server/proxy protocol mismatch. Keep authentication and secure-profile settings intact while collecting the exact error.

What it means

Signed chat carries identity and message metadata. Proxies, chat formatters, protocol translators and some client mods can mishandle the signature chain or acknowledgements.

If you are a player

  • Restart the official launcher session and test with a clean client build matching the server.
  • Note whether only chat fails, or the entire connection closes after sending a message.

If you run the server

  1. Collect the full server and proxy log around the failure, including the first chat-validation warning.
  2. Check that chat/translation plugins and the proxy are built for the active Minecraft version.
  3. On a private staging server, test without a chat-altering plugin to find which component changes message handling.
  4. Compare signed-chat behavior through the proxy versus a safely isolated backend.

Confirm the fix: Avoid turning off online authentication or applying unreviewed “disable secure chat” workarounds to a public server.

Important notes

  • If Velocity logs A plugin tried to cancel a signed chat message, use the current Velocity guidance for signed chat/plugin compatibility rather than simply disabling secure-profile checks.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000