PanelicaDocs
panelica.com
Docs / Tools & Settings / Repair Tool

Repair Tool

Panelica 1.0.375 Verified 2026-07-24 Tools & Settings

The Repair Tool is Panelica's "fix common problems" button: it scans the server for the faults that usually take a panel or a site down, services that stopped, a broken config, a full disk, wrong file ownership, and offers a safe one-click fix for each. Every fix previews what it will do, asks for confirmation, and is built to be idempotent; the config regeneration additionally rolls back per domain if anything fails.

Panel locationRepair Toolhttps://YOUR-SERVER-IP:8443/repair (ROOT only)
 Repair Tool
Total
22
OK
20
Warning
1
Critical
1
critical panelica-mysql stopped · Fix: restart

What it checks

On open, the tool scans the server and lists findings worst-first, each with a severity (ok, info, warning, critical), what it found, and a Fix button where a repair is available. The checks cover:

  • Services: every core service (backend, external API, the two nginx instances, Apache, PostgreSQL, MySQL, Redis, BIND, the FTP server, fail2ban). A stopped-but-enabled service is critical and fixable; a service in a boot transition is reported calmly as info, not a false alarm.
  • Sockets: the three critical Unix sockets (Redis, MySQL, PostgreSQL) exist on disk; a missing socket means the service crashed.
  • Configs: nginx, Apache and BIND configs pass their own validators (nginx -t, httpd -t, named-checkconf); the customer nginx config is regenerable if broken.
  • Disk: the root and /opt/panelica filesystems against 85% (warning) and 95% (critical) thresholds.
  • Home permissions: each customer's home directory is owned by their own account, the wrong-ownership fault that mysteriously breaks a site.
Behind the scenes, why this engine is trustworthy: the repair engine is deliberately independent of the panel backend, it talks only to the OS (systemd, the filesystem, config validators). That is what lets the same engine also power the rescue console on port 8444 when the backend itself is down. Every check runs with a timeout and panic isolation, so one hung or broken check never freezes the scan, and an unknown severity is always shown as critical rather than hidden.

The fixes, and why they are safe

Repairs are never automatic; you press Fix, see a preview of exactly what will happen, and confirm.

Fix What it does, safely
Restart service Restarts only a stopped service (a healthy one is a no-op), validates the unit name, and verifies the service is actually running afterward, not just that the command returned
Clean up disk Deletes only from an allow-list (old temp, trash, expired cache, and rotated, never live, logs); it never walks databases, backups, quarantine or user data, and re-checks each file is a real file right before deleting
Regenerate config Rebuilds the customer nginx vhosts from the database using the same backup-test-rollback path every domain operation uses, so a broken domain can never take the others down and a bad config never loads
Reset permissions Restores a customer's home to Panelica's ownership model (not a blind recursive chown), fixing root-owned files under public_html while preserving the special log and session groups; deletes nothing
Fix common problems Re-runs every idempotent startup self-heal on demand (over twenty of them), each guarded and safe to repeat
Destructive fixes ask twice. A fix that deletes (disk cleanup) or rewrites configs (config regenerate) requires typing a confirmation and, for cleanup, shows the exact files and size first; a non-destructive fix (restart, permission reset) asks a plain confirmation. Every applied fix is written to the audit log. Note that the two genuinely destructive-adjacent operations, disk cleanup and config regenerate, are the ones with the strongest safety rails (allow-list and per-domain rollback), so the tool is safe to reach for when something is actually broken.

Access

Strictly ROOT, at both the route and the backend, with every applied fix audited. See roles and permissions. When the panel backend itself is down and you cannot reach this page, the same repairs are available from the rescue console on port 8444.

Panelica Documentation · Written and verified against the live panel. · Last verified 2026-07-24 on Panelica 1.0.375