[Bug] Random timeout on connect, connectionhandler fires, joined handler never does #367
Replies: 4 comments 7 replies
|
Thanks, was able to reproduce it by reducing the timeout value. Will check. |
|
Can you upload your log file? I can only reproduce it with timeout values less then 15sec which is expected since thats the keep alive interval. |
|
Sure. I think this is one of them: |
|
Also please check if increasing sv_clientConnectingTimeoutMilliseconds helps. This is by default 60000. |
|
Sure, I'll set it to 120 seconds. My connection does usually complete around 60 seconds, so it might be this. 60 seconds by default is pretty low though. I have a high-end PC and it takes me a minute to connect, imagine someone with a slower network or PC. Then again, connection times on enhanced are really bad. On legacy, connecting would take like 10 - 15 seconds tops. Improving the connection speed would be a much better solution, if possible. |
|
We have keep alives that fire every 15 seconds. So that would mean for some reason at least 4 got missed. |
|
Also can you check in your server when the client gets timeouted in combination with the client log. |
|
Yeah I checked every time. Nothing really shows there. I see the playerconnecting log line that happens when you connect to a server. but the playerjoined event never logs, it gets stuck somewhere in between |
|
A fix for this bug has been implemented and is available in August 11 Patch. Please try again and let us know if the issue persists. Thanks for your help! |
|
So far it seems to work. But prior to this patch it would also not happen every day. So I'll keep testing for a bit |
|
I still have this issue, running Linux server build 119. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
I posted it as a comment on #11 but that issue has been closed it seems. However, on the latest build (b110) it still randomly happens and is really annoying. You wait for the entire loading screen to finish only to end up with a timeout...
Prior to this build, it would stop at that log line and wait forever. Now, it waits for a few seconds and kicks you of the game with a Connect lost. Timeout: true message. Hardly an improvement I would say.
Appears to be related to server-side, since only a server restart seems to fix it. Client-side reconnect keeps failing if you keep trying without a server restart.
Issue type
Both / Unsure
Repro rate
Sometimes
Server build version
b110
OS
Windows 11
CPU
Intel Core i7-12700K
GPU
NVidia RTX 5070TI
RAM
96GB DDR4
Storage type
SSD NVMe
Connection type
Ethernet
ISP and bandwidth
1GB up/down Glass Fiber
DxDiag
No response
Network graph
No response
Platform
Docker
OS version / distribution
Alpine minirootfs 3.20.10-x86_64
CPU
Intel Core i7-12700K
RAM
96GB DDR4
Using txAdmin?
No
Hosting provider
Self-hosted
Machine type
None
/perf endpoint output
No response
DDoS protection
No response
ulimit -n value (Linux only)
1048576
Docker Compose file (Docker only)
No response
Steps to Reproduce
I don't know. it happens randomly..
Expected Behavior
Should not timeout for no apparent reason
Actual Behavior
It times out during loading screen after client obtains client ID and attempts to do UDP handshake
Evidence
No response
Additional Context
I am using the .NET 10 module if that matters.
All reactions