Skip to content
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

Failed to validate message acknowledgements #1127

Open
7wOv6ySCjo opened this issue Oct 28, 2023 · 10 comments
Open

Failed to validate message acknowledgements #1127

7wOv6ySCjo opened this issue Oct 28, 2023 · 10 comments
Labels
type: bug Something isn't working

Comments

@7wOv6ySCjo
Copy link

Hello everybody. I built a minecraft:tellraw command on the page: www.minecraftjson.com

I run this command in the console of my backend server Paper:
minecraft:tellraw Sistan ["",{"text":"JUEGOS:","bold":true,"color":"#F97603"}," ","Sistan"," acaba de completar el parkour ",{"text":"[Angeles]","color":"dark_purple","clickEvent":{"action":"run_command","value":"/angeles"},"hoverEvent":{"action":"show_text","contents":[{"text":"Hacé click para ir","color":"green"}]}}]

The tellraw message arrives at the client Minecraft 1.19.4 and I simply click on one of the hoverEvent in the message. Velocity kicks me with: Failed to validate message acknowledgements from Sistan

Logs:
Velocity:

[04:25:57.642] [Velocity Async Event Executor - #14/INFO] [com.velocitypowered.proxy.protocol.packet.chat.CommandHandler]: [connected player] Sistan (/###.###.##.###:63108) -> executed command /angeles
[04:25:57.668] [Netty epoll Worker #13/INFO] [com.velocitypowered.proxy.connection.client.ConnectedPlayer]: [connected player] Sistan (/###.###.##.###:63108): kicked from server survival_oscuro: 
[04:25:57.668] [Netty epoll Worker #13/INFO] [com.velocitypowered.proxy.connection.MinecraftConnection]: [server connection] Sistan -> survival_oscuro has disconnected

Backend:

[04:25:57.643] [Netty Epoll Server IO #3/WARN]: Failed to validate message acknowledgements from Sistan
[04:25:57.661] [Server thread/INFO]: Sistan lost connection: Chat message validation failure

What solution could I use to prevent this from happening? It is happening massively.

@456dev
Copy link

456dev commented Nov 20, 2023

does just running the command "/angeles" manually cause the same issue?
does it occur with any other commands in the tellraw?

@4drian3d 4drian3d added type: bug Something isn't working status: awaiting response More information is required labels Jan 19, 2024
@4drian3d 4drian3d changed the title Failed to validate message acknowledgements for ... Wait... what? Failed to validate message acknowledgements Jan 29, 2024
@7wOv6ySCjo
Copy link
Author

does just running the command "/angeles" manually cause the same issue? does it occur with any other commands in the tellraw?

happens with any clickable command in the message.

@4drian3d 4drian3d removed the status: awaiting response More information is required label Feb 2, 2024
@Jeremylo1
Copy link

Jeremylo1 commented Feb 14, 2024

does just running the command "/angeles" manually cause the same issue? does it occur with any other commands in the tellraw?

I encounter the same problem! From time to time a same clickable message sent with tellraw command can be executed or disconnect the player with the following message in the console :
[02:00:42 WARN]: Failed to validate message acknowledgements from Jeremylo1

@JonnygamingTv

This comment was marked as off-topic.

@gamer50082
Copy link

This is velocity thou and your using bungeecord

@ArikSquad
Copy link

Same issue, can't click any "links for commands" in chat.

@7wOv6ySCjo
Copy link
Author

We still do not have an approaching solution to this problem? the problem persists.

@Mitchel387
Copy link

Mitchel387 commented Mar 16, 2024

I'm also having this issue for a month now. It doesn't happen when when we type the commands by ourselfs. But clicking on command links does kick players sometimes. I use Velocity 3.3.0-SNAPSHOT & Paper version git-Paper-450 (MC: 1.20.4) (Implementing API version 1.20.4-R0.1-SNAPSHOT) (Git: 62b220a). We use the /tpa commands of HuskHomes. If you need more technical info, I'm happy to help! I hope I can write some "Steps To Reproduce" for you.

Here the typical messages in console of kicked players clicking on tpa accept text in chat.

[14:30:17 INFO]: Player_1 issued server command: /tpa Player_2
[14:30:20 WARN]: Failed to validate message acknowledgements from Player_2
[14:30:20 INFO]: Player_2 lost connection: Chat message validation failure
[14:30:20 INFO]: Player_2 left the game

I'm running HuskHomes 4.5.5. So I will try to update this plugin to the latest release and see if this bug still occurs.
One thing I noticed is that it isn't reported in the velocity console that a player has been kicked. So maybe it's a bug of the specific plugin.

[Update]: Updating the plugin to the latest version didn't solve the issue unfortunately.

@Jeremylo1
Copy link

This is the case for all clickable messages in the chat, regardless of the plugin used. In fact, even if the server doesn't contain any plugins, this issue still occurs. However, the problem only arises after the player has been connected for a certain amount of time. If the player disconnects and reconnects, they can click on the message without any issues. But if they have been connected for at least an hour, it will disconnect them.

@NinjagoKristian
Copy link

This is the case for all clickable messages in the chat, regardless of the plugin used. In fact, even if the server doesn't contain any plugins, this issue still occurs. However, the problem only arises after the player has been connected for a certain amount of time. If the player disconnects and reconnects, they can click on the message without any issues. But if they have been connected for at least an hour, it will disconnect them.

Same thing happens here with my custom plugin, exactly what you said "the problem only arises after the player has been connected for a certain amount of time".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

9 participants