Connection timeout issues

[TheRandomLabs]

Some users seem to be experiencing timeout issues even with this mod installed. (See #94)
If you have this problem, can you make sure that your KeepAlive packet interval is set to 15 seconds? Keep in mind that the read timeout is specified in seconds, but the login timeout is specified in ticks.
If you can also ensure that a message like this: on 1.14+
occurs in the console, that would be great. The message doesn't seem to appear in the log because of some weird Forge stuff.
A reminder that the timeout options are server-sided (except for the read timeout which has some client-sided functionality). The configuration options will be less confusing in the 1.16.4 rewrite.
EDIT: In the rewrite, the configuration options are better-organised and documented.

[Diversion98]

Hi!

Im running a server (MC Eternal 1.3.7.1) and I added the latest version of randompatches to the server (1.12.2-1.22.1.10).
There are now 3 players out of 18 that cant join because a time out.
If I delete the randompatches mod, they can just join fine.

I increased the timings as follow:
keepalive = 15
loginTimeout=360000
I:readTimeout=900000

But it just seems it gets ignored.

Also I dont get the RandomPatches ServerLoginNetHandler Transformer message in the console.

[TheRandomLabs]

Whoops, that message is only for 1.14+.
That's annoying; can you send me a debug.log?
Also, did the default configuration cause the same problem?

[TheRandomLabs]

If someone is experiencing this on 1.16.4, can they check if 2.1.0 fixes this issue (Forge/Fabric)?

[Ryorama]

I don’t know if I should open a new issue(I just put this here as it’s an existing issue). Anyway, the error keeps occurring for me as well on 1.16.4 with the mod version being 2.1.2. I’m also using the fabric version.

[x13x54]

EDIT: I traced my issue back to the login mod mentioned below. The mod has gone through many improvements since the version we were using and the timeout issue has been fixed in the latest version. If you are running this mod, update it if you see one of these error in the server console: [Server thread/INFO] [net.minecraft.network.play.ServerPlayNetHandler/]: <player> lost connection: Login timed out OR [Server thread/INFO] [net.minecraft.network.play.ServerPlayNetHandler/]: <player> lost connection: Login timeout

While going through server config today i found that a different mod called SimpleLogin has a default login timeout of 60 seconds.
Changing this value in <server>/<world>/serverconfig/simplelogin-server.toml and then doing a server restart appears to have fixed the login timeout issue that our players have occasionally suffered.

Perhaps this is one of the causes for this for some other people as well? When searching for "minecraft login mod" the simplelogin mod is all the way at the top..

Exact error message we got exactly 60 seconds after first sign of login: [18May2021 16:20:43.563] [Server thread/INFO] [net.minecraft.network.play.ServerPlayNetHandler/]: x13 lost connection: Login timed out. (I now believe this to be an error from the login mod timing out)

We have instructed players to add -Dfml.readTimeout=600 (even though forge removed it) to their java options and set their randompatches timeouts to 20 minutes before, but this had no clear effect prior to changing the simplelogin timeout value.

We're running this on an 8GB (ddr3) ram linux VPS with a openj9 java VM.
Versions:
RandomPatches 2.4.4
Minecraft 1.16.5
Forge 36.1.2
AllTheMods6 1.5.8b
SimpleLogin 1.16-0.0.0

PS: In case it's not clear to anyone, the server i have found this issue on has online-mode=false in it's server.properties and is used by a closed group of friends as opposed to a fully public online server. This might lead to the error message being different as well as this solution not applying to people who have their server configured differently.