We use the server restart feature (via both the API and the web panel) for our production and staging experiences in different contexts. For some reason, as of recent, neither method of restarting servers works properly on our staging experience: it disconnects players instead of teleporting/reconnecting them.
A private message is associated with this bug report
Hello jackTabsCode!
Thank you for reporting this. Could you upload the logs from the client experiencing the disconnect into the private message on this thread?
We’re also experiencing this and this has broken our shutdown notifications for players, although we occasionally get error code 288 “the server has shut down” rather than 301. Only main difference for the messaging I can imagine is we intentionally introduce a delay in the shutdown process via BindToClose so that we can show UI to players saying the game is restarting.
This occurs whether or not we use BindToClose.
Relevant client log snippet:
2026-01-31T16:32:05.763Z,3776.763184,5cc8,6 [FLog::Warning] [... snip, just our warn() output ...]
-- server shutdown occurs here, with 2 second delay introduced via BindToClose
2026-01-31T16:32:07.888Z,3778.888672,7754,7 [FLog::Network] Disconnect reason received: 301
2026-01-31T16:32:07.909Z,3778.909668,7754,7 [FLog::Network] Connection lost
2026-01-31T16:32:07.909Z,3778.909668,7754,7 [FLog::Network] Connection lost: connectMode: Peer Disconnected, timeMS:3778909, connectionTime 3683230
2026-01-31T16:32:07.909Z,3778.909668,7754,7 [FLog::Network] Connection lost: AckTimeout 0, IsOutgoingDataWaiting 0
2026-01-31T16:32:07.909Z,3778.909668,7754,7 [FLog::Network] Disconnection Notification. Reason: 301
2026-01-31T16:32:07.914Z,3778.914551,5cc8,7 [FLog::Network] Disconnect from xxx: ID_DISCONNECTION_NOTIFICATION
2026-01-31T16:32:07.914Z,3778.914551,5cc8,6 [FLog::Output] Disconnect from xxx
2026-01-31T16:32:07.914Z,3778.914551,5cc8,7 [FLog::Network] Client has been disconnected with reason: Disconnected from game, please reconnect
2026-01-31T16:32:07.915Z,3778.915527,a190,6,Error [logGroup] Client Peer updating state from Connected -> Closed: draining state on receive, reason RCC: 288
2026-01-31T16:32:07.915Z,3778.915527,5cc8,6 [FLog::Output] Session Transition FSM: Error Occurred.
2026-01-31T16:32:07.915Z,3778.915527,5cc8,6,Info [FLog::AppMemUsageStatus] 3784003596.0
2026-01-31T16:32:07.920Z,3778.920410,5cc8,7 [FLog::Network] Time to disconnect replication data: 0.350500
2026-01-31T16:32:07.921Z,3778.921631,5cc8,7 [FLog::Network] Sending disconnect with reason: 301
2026-01-31T16:32:07.921Z,3778.921631,5cc8,6,Info [DFLog::RbxTransportDummyClient] Connection closed by server for reason: RCC: 288
2026-01-31T16:32:08.266Z,3779.266846,a190,6,Info [DFLog::RbxTransportDummyClient] Ping thread exiting
Can also send a full client log if necessary.
Hope this can be resolved soon! Its not good when updating our games.
Hi, is this still happening for anyone? Please send over a recent client log if so. Thanks so much!
Hi all, closing this for now since there hasn’t been any recent reports and we’re unable to reproduce. Please let us know if this issue comes up again.
Thank you!