Fix a Console stuck on Reconnecting

The Console tab shows your server's output live. That feed runs over a connection between your browser and the machine your server lives on. When the connection drops, a small status chip appears in the console's header bar and the feed stops moving. Your game server itself keeps running on our hardware while this happens, so you haven't lost anything. Only your view of it has gone quiet.

What the chip says

The chip only shows while the connection isn't healthy, and it disappears once you're connected. On a phone it shows just an icon.

After a drop the page retries automatically, waiting a little longer between tries, up to 30 seconds. If it can't get through at all on its first attempts, it switches to a backup route through our servers so the console keeps working. Most blips fix themselves.

Fix it

Work down this list and stop when the chip goes away.

1. Wait half a minute. The automatic retry often catches a short network wobble.
2. Check your own connection. Open another website. If you're on a VPN, a hotspot or hotel Wi-Fi, switch it off or change network and see if the chip clears. Browser extensions that block scripts or live connections can also stop the console, so try a private window with extensions off.
3. Reload the page. Reloading opens a fresh connection. If it still says Reconnecting…, do a hard reload, which ignores the cached copy of the page. In Chrome that is Ctrl+Shift+R or Shift+F5 on Windows and Cmd+Shift+R on a Mac. Other browsers have their own shortcut for it.
4. Try another browser or device. If that works, the problem is on the first browser or its network.
5. Check the other tabs. Open File Manager and Backups. If they show "Could not load directory." or "Could not load backups.", your connection to the whole site is the issue and not just the console feed.

Commands you type while it's down

Anything you send while the console isn't ready isn't lost. The console is ready only when the connection is up and the game server is running. Otherwise it holds your command in a queue and shows "queued, will send on reconnect" with a Manage queue button. The commands are sent in order once both are true again, so a stopped server keeps them waiting after the connection returns. The queue lives in your browser tab for this session, so open Manage queue and remove anything you no longer want before the console is ready again, such as a stop or a ban. Use your server's console explains the command box and the queue.

When to ask us

Open a ticket if the chip is still Reconnecting… or Error after a hard reload on a second network. Include your browser and version, the time it started, whether other pages on the site load, and which chip you see. Contact support and open a ticket shows how.