Backups, health & integrity check

Three admin-only pages that answer "is this installation in good shape": Backups, Status and Integrity check.

Backup Manager

In the sidebar, go to System > Backups. Database backups are created automatically, on a schedule — this page is an overview, not a trigger.

Backup Manager: an overview of the automatic database backups.

Backups are created hourly by the cron daemon via pg_dump, following the schedule and rotation set in the backup conflines, into a backup folder on the server. Restoring and downloading a backup through this page are not available yet — a restore is a manual pg_restore on the server.

System status ("doctor")

In the sidebar, go to System > Status. This is the closest thing to a health check / doctor page: every core service at a glance, with restart buttons and a reboot-survival check, refreshing automatically every 10 seconds.

System status: services, connection checks and reboot survival.
SectionShows
ServicesPostgreSQL, Asterisk (PBX), Nginx, fail2ban (brute-force protection), the firewall and GeoIP timers, and the web/background processes — each with a status dot, restart count and its own Restart button.
Connection checksLive checks such as the PostgreSQL connection latency, Asterisk AMI uptime, and whether FastAGI (call routing) is reachable.
Reboot survivalWhether each service is set to start automatically after a server reboot.
Warning

The Restart buttons are real: each one restarts a live service on this server. This wiki only looks at the page — it does not press any of them.

Integrity check

In the sidebar, go to System > Integrity check. A read-only report on configuration and security issues, checked live each time you open the page — nothing here is fixed automatically.

Integrity check: eight read-only checks, each OK or listing its problem rows.
CheckFlags
Destinations without groupDestinations not assigned to any destination group.
Unprocessed error actionsFailed background actions not yet marked as reviewed — these stay listed until marked "Done", even after the underlying cause is fixed.
Devices with a weak passwordDevice (SIP) secrets shorter than 8 characters.
Users with weak passwordCustomer accounts with an empty or trivial password.
Postpaid + allowed loss callsUsers set to postpaid and allowed to make calls the system cannot bill — a risky combination.
Insecure SIP devicesDevices without transport encryption.
Servers with low free spaceAny server approaching its disk space limit.
Emergency numbers as extensionAn emergency or service number reused as a device, ring group, queue or DID extension.

Check

Open Status and confirm every service shows a green dot; open Integrity check and confirm nothing new appears that was not there the last time you looked.