Nextcloud CODE Editing Sessions End Prematurely Due to Proxy Timeouts
A persistent 10-minute disconnection during Nextcloud CODE editing sessions is often caused by proxy or load balancer timeouts.
CODE editing sessions can unexpectedly terminate after approximately 10 minutes due to idle timeouts in reverse proxies or load balancers, which can be identified by inspecting WebSocket paths and checking connection logs. The issue arises when the WebSocket connection, crucial for real-time collaboration, is prematurely closed by an intermediary component.
Collabora Online, integrated with Nextcloud, relies on a dedicated WebSocket route for document sessions. To resolve this, administrators should extend proxy read and send timeouts beyond the expected editing session duration and ensure the correct WebSocket route is configured, referencing Collabora’s official proxy examples and Nextcloud’s Docker examples.
Troubleshooting involves verifying connectivity in both directions, examining logs for errors, and adjusting timeouts at each intermediary layer, as WebSocket traffic can traverse multiple components. It’s important to distinguish this from document idle-unload settings and to confirm that changes effectively address the disconnection issue.