#Server Stall After Registration Failure / Recovery

1 messages · Page 1 of 1 (latest)

worthy cove
#

Server stall is caused by repeated Coop backend registration failure followed by incomplete recovery.

At startup:

[13:58:49] RegisterServer process begins

Immediately after, the CM/API gateway fails repeatedly:

error_code UNAVAILABLE
error_message 'Received http2 header with status: 502'

and

Cm disconnected. Try to reconnect.
Status 14 ('Received http2 header with status: 502')

This causes:

GcStream is broken.
ErrorMessage 'Server registration finished with error'
State WaitingForRegistration

followed by:

Cannot create Coop NetServer.
Error Server registration finished with error

This is the first blocking failure, the Coop NetServer cannot be created because registration failed.

After multiple retries (~7 reconnects), registration eventually succeeds:

Process OnRegistration.
Result CmResult_ResultType_Success

and

GsStream. Change state.
Registration => Connected

However, after this point the server does not continue normal startup. There is no further Coop/DataKeeper progression, no session/world transition, and no shutdown/crash. The log only shows periodic monitor entries like:

CheckMonitor::PrintReport

Memory remains stable (~514–522 MB), so this is not an OOM or crash.

Conclusion:
The trigger is upstream gateway instability (HTTP 502 causing gRPC UNAVAILABLE). The actual “stall” is likely a state-machine bug after reconnect: registration recovers successfully, but the server fails to resume the post-registration startup path (likely around UR5CoopProxyServer / UR5DataKeeperForServerCoop reconnect handling).

sick fiber
#

Thanks for the report. Please provide a bit more context on your environment - both server and client machines.

worthy cove
#

This is a Nitrado-hosted package, and the issue occurs at least once per day where the server stalls as described above.

According to the hosting package dashboard, the server still shows as running, but when attempting to connect from any client, the loading screen appears for about one second before returning the player to the main menu. This happens because the server enters a hung state and is unable to process incoming connections.

The issue is consistent across all clients and is not client-side. The normal process is:

Press:
Play
Connect to server (it appears under Recently Played)
Select the server
Enter the password
Press Connect

At that point, the “Loading…” screen briefly appears, then the client is immediately returned to the main menu.

Since every client experiences the exact same behavior whenever the server stalls, this confirms the issue is with the server hanging rather than with any individual client setup.

sick fiber
#

thanks for the update, I think a <@&1494048605265465539> specialist can help with this, when available.

north oriole
#

I would need service/user ID to be able to check the server and see what can be done