«Connecting to daemon...» looks exactly like the server has gone down, and the actual game process on the other end of it is very often running perfectly normally the entire time you are staring at that message.
The console window is a window, not the server
The live console uses a WebSocket — a persistent, two-way connection your browser opens to stream console output in real time, distinct from the ordinary page loads the rest of the panel uses. That connection lives entirely in your browser tab. A backgrounded tab a browser has throttled, a laptop that slept, a brief local network drop, or a session token that expired can all sever it — none of which touches the actual server process running on the node, which has no idea your browser lost its view and keeps ticking exactly as before.
Telling the two apart
| What you see | What it means |
|---|---|
| Console shows «Connecting to daemon...» | Your browser's WebSocket dropped. Check if players can still connect in-game — if they can, the server is fine. |
| Console loads but shows no new output | Also usually the browser tab; reload the page. |
| Players cannot connect either | This is the server itself, not the console view — a different problem. |
A full page reload (F5) re-establishes the WebSocket cleanly in a few seconds. Restarting the actual server to fix a console display issue ends every player's session for no reason, when the process was never the thing that was broken.