Players getting timed out

[KhrysAK47]

Expected Behavior

Players should not be kicked randomly.

Actual Behavior

[00:04:57] [Netty epoll Worker #3/INFO] [com.velocitypowered.proxy.connection.client.ConnectedPlayer]: [connected player] Enderzombie44 (/163.117.104.252:50180) has disconnected: An internal error occurred in your connection. [00:04:57] [Netty epoll Worker #3/ERROR] [com.velocitypowered.proxy.connection.MinecraftConnection]: [connected player] Enderzombie44 (/163.117.104.252:50180): read timed out

Players are getting kicked randomly.

Steps to Reproduce

https://pastebin.com/dnpJYEtG

Plugin List

There are no plugins currently installed.

Velocity Version

[11:49:33 INFO]: Velocity 3.3.0-SNAPSHOT (git-0cd069ec-b431) [11:49:33 INFO]: Copyright 2018-2024 Velocity Contributors. Velocity is licensed under the terms of the GNU General Public License v3. [11:49:33 INFO]: velocitypowered.com - GitHub

Additional Information

No response

[bolda500]

I have the same problem, and I assume I don't have the same plugins as the guy above. Sometimes the connection is broken a dozen or so seconds after connecting and sometimes after a longer time. On average, a player is kicked out every few minutes, with 60-70 online.

Below is the error log.

ERROR censored-nick (/77.222..:22421): exception encountered in com.velocitypowered.proxy.connection.client.ClientPlaySessionHandler@31984e67 10.10 23:12:17 [Server] INFO io.netty.channel.unix.Errors$NativeIoException: recvAddress(..) failed: Connection reset by peer

[Stis780]

Yes sir! We have exact the same problem, a bunch of people gets disconnected, usually around peak, probably high load or some kind of race condition? it's still bad they get kicked off the proxy

[electronicboy]

connection reset by peer means that the connection was closed externally to the proxy; read timed out means that the proxy didn't get any packets in 30 seconds on that connection;

Diagnosing these types of things is generally hard, especially with 0 information, large amounts of disconnects at once would generally be networking issues or something, like a plugin, stalling out a network pipeline thread. without figuring out a way to throw a lot of monitoring into your specific setups, it's generally not tenable for us to advise much here

[Stis780]

Update netty? I know it's hard to do this, is there any way we can help? How?

[electronicboy]

updating netty to the latest 4.1 release would be trivial, but there have been no updates that would be relevant to connections being closed externally

[bolda500]

sorry if I misled you, I changed the network_compression_threshold from 512 to 64 and the problem disappeared, I don't know why it was set like that but now it's ok, I also changed the version of Velocity to the last build of 3.4.0 but I don't know if it has anything to do with it. I will try to monitor closely whether the problem still occurs. Thank you for your time.

[Stis780]

On velocity? Isn't default there 256?

[Stis780]

BTW Also not sure if this is intended but https://papermc.io/downloads/velocity still defaults to 3.3.0

[Timongcraft]

BTW Also not sure if this is intended but https://papermc.io/downloads/velocity still defaults to 3.3.0

Already reported: https://github.com/PaperMC/docs/issues/487 (reference: https://discord.com/channels/289587909051416579/947676006964162611/1293570377288650793)

[bolda500]

On velocity? Isn't default there 256?

of course it is, but it's possible that I changed something by mistake.

[Stis780]

@bolda500 did this improve things in any meaningful way? I was already using 256 and the issue still occurs...

[bolda500]

@bolda500 did this improve things in any meaningful way? I was already using 256 and the issue still occurs...

After changing the value to 64, or I guess 128 would also be good, the problem disappeared. I also changed the connection-timeout value from 5000 to 7000.