What Happens When the Panel Itself Won't Load
Every panel has a blind spot: what do you do when the panel is the thing that is broken? If the backend crashes, the database goes down, or nginx fails to start after a bad config change, the usual answer is opening a support ticket with your hosting provider for console access, or waiting for a rescue-mode reboot.
Panelica ships with its own answer to that problem: Rescue Mode, a separate recovery service that stays up independently of the panel it is rescuing.
What It Does
Rescue Mode runs on port 8444, as its own standalone binary with no dependency on the main backend, the database, or nginx. It is built to start on boot and stay running through a crash of everything else on the server — including a watchdog that restarts it if it ever hangs, and out-of-memory protection so it is not the first thing killed if memory runs low.
Once you log in with the server's root system password, Rescue Mode gives you three things:
System Overview
A single screen with hostname, OS, kernel version, uptime, load average, CPU count, memory and swap usage, disk usage, listening ports, the top resource-consuming processes, any failed background services, recent login history, and recent error log lines — everything you would normally piece together with five different commands.
Diagnostics and Repair
The same fix engine used by the panel's Repair Tool is available here: restart a specific service, regenerate a broken configuration, free up disk space, or fix a user's file permissions — all from Rescue Mode, even while the main panel is completely unreachable. A dedicated Quick Actions panel also offers a service restart selector and a server reboot option, both requiring confirmation.
Root Terminal
A full terminal session, connected over a WebSocket to a real shell on the server, embedded directly in the Rescue Mode page. No separate SSH client needed — just a browser.
How to Use It
- If your Panelica panel at port 8443 stops responding, open
https://your-server-ip:8444in a browser instead. - Log in with the server's root system password — the same one used for SSH.
- Check the Overview tab first: failed services, high load, or a full disk are usually visible immediately.
- Use Diagnostics & Repair to apply the fix that matches what you found — restarting the crashed service is often enough.
- If you need to run something manually, open the Root Terminal tab instead of starting a separate SSH session.
- Once the underlying problem is fixed, the main panel at port 8443 comes back on its own.
Why It Matters
A hosting panel that goes down with no way back in except a provider ticket or a rescue-boot reinstall is a single point of failure. Rescue Mode exists because the panel, the database, and nginx crashing should not mean losing access to the server that is still running underneath them. It is a lightweight, independent safety net that is there specifically for the moment everything else is not working.
Get it now: Rescue Mode is available on the latest Panelica release and starts automatically on boot. Update your panel, then keep https://your-server-ip:8444 bookmarked for the day you need it.
Frequently Asked Questions
Does Rescue Mode need the main panel to be running?
No. It runs as an independent process with no dependency on the panel backend, the database, or nginx.
What password do I use to log into Rescue Mode?
The server's root system password — the same one you would use for SSH.
Does Rescue Mode start automatically?
Yes. It is installed as a system service that starts on boot and restarts itself if it ever stops responding.