Server client connection: lost connection: Took too long to log in

[FlambeSk]

Describe the bug
When player ( client ) trying connect on server, server gets error: lost connection: Took too long to log in
Server is set to offline mode event this is still trying to connect on Mojang servers for authentication.

Server is with 8Gb RAM.

All other servers are working correctly. There is no problem with TCP connection.

Edit
I just tested ATM-5 and everything works great. On ATM-6 problem only.

[shaoiken]

I can atleast confirm that you are not alone with that problem. I play together with a friend on a private server and she is experiencing the same issue with ATM-6 on the 1.16.3 versions. On the older 1.16.1 one it was no problem.

We too tried to set the server to offline mode which did not help and tried to extend the timeout via java startup parameter Dfml.readTimeout=360 on the server & client, but that didn't help either.

[ViRb3]

The login timeout is being overriden by RandomPatches. To adjust this, edit /config/randompatches.toml:

# Options related to the disconnect timeouts.
[timeouts]
	# The interval at which the server sends the KeepAlive packet.
	# Min: 1
	# Max: 2147483647
	# Default: 15
	keepAlivePacketInterval = 15
	# The read timeout in seconds.
	# This is the time it takes for a player to be disconnected after not responding to a KeepAlive packet.
	# This value is automatically rounded up to a product of keepAlivePacketInterval.
	# Min: 1
	# Max: 2147483647
	# Default: 90
	readTimeout = 90
	# The login timeout in seconds.
	# Min: 1
	# Max: 2147483647
	# Default: 900
	loginTimeout = 900

[FlambeSk]

The login timeout is being overriden by RandomPatches. To adjust this, edit /config/randompatches.toml:

# Options related to the disconnect timeouts.
[timeouts]
	# The interval at which the server sends the KeepAlive packet.
	# Min: 1
	# Max: 2147483647
	# Default: 15
	keepAlivePacketInterval = 15
	# The read timeout in seconds.
	# This is the time it takes for a player to be disconnected after not responding to a KeepAlive packet.
	# This value is automatically rounded up to a product of keepAlivePacketInterval.
	# Min: 1
	# Max: 2147483647
	# Default: 90
	readTimeout = 90
	# The login timeout in seconds.
	# Min: 1
	# Max: 2147483647
	# Default: 900
	loginTimeout = 900

This worked, thank you so much !

[ViRb3]

@FlambeSk For the record, which value did you adjust, and to how much? I'm looking to submit a PR with this change as a lot of people are having the problem, but my computer is too fast to encounter it 😅

[FlambeSk]

Here are values what I set 👍

[timeouts]
# The interval at which the server sends the KeepAlive packet.
# Min: 1
# Max: 2147483647
# Default: 15
keepAlivePacketInterval = 500
# The read timeout in seconds.
# This is the time it takes for a player to be disconnected after not responding to a KeepAlive packet.
# This value is automatically rounded up to a product of keepAlivePacketInterval.
# Min: 1
# Max: 2147483647
# Default: 90
readTimeout = 500
# The login timeout in seconds.
# Min: 1
# Max: 2147483647
# Default: 900
loginTimeout = 9000

[shaoiken]

Did you adjust it only on the server or the client as well?

[FlambeSk]

Did you adjust it only on the server or the client as well?

Only server. It took little longer for client to connect ( maybe 1 minute ), but then client connects.