billingHelp

Health, jobs, self-check and system monitor

The scheduler and its jobs, the security self-check, the system monitor with configuration advice, and /health for external monitoring.

Health & jobs#

  • Scheduler — whether jobs are driven by system cron, by the cron URL, or by page views (pseudo-cron), and when it last ticked.
  • Jobs — every job with its schedule, last run, result and next run. Run now runs one job immediately.
  • Recent runs — results and errors.
  • Email outbox, Database, Disk and Routing (clean URLs or entry files).

Jobs run only on the writable server of a pair.

Self-check#

Self-check runs the deployment and security checks: PHP and MariaDB versions, extensions, Argon2id, app/ and data/ outside the webroot, key and config permissions, database users and least-privilege grants, security headers, that webhook endpoints refuse forged signatures, backup freshness and off-box copies, test credentials on live products, licensing keys, GeoIP freshness, the static SEO files, the help pages and the bundled fonts.

Each check is Pass, Warn or Fail, with the detail needed to fix it. It runs daily (failures are emailed to super admins) and from the command line:

sudo -u www-data php app/cli.php selfcheck   # exit code 1 when anything fails

Security checks#

CheckWhat it provesIf it does not pass
Every route requires the right sign-in, capability and CSRF checkThe route table follows the access rules: private areas need their sign-in, state-changing routes keep the form token, no write is open to the read-only role.Only after a local code change: undo it, or copy the release again.
Forged form submissions are refusedA form from another site, without the token or without an Origin is rejected by the running code; signed in, only the token of that session is accepted.Copy the release again.
Session cookies are HttpOnly, Secure, SameSite and host-boundThe cookie settings used over HTTPS.Copy the release again.
PHP runtime settingsdisplay_errors and expose_php are off, allow_url_include is off. Read from PHP-FPM, so run it from this page.Set them in the FPM php.ini; see Hardening the server.
Application code is read-only for PHPThe PHP user cannot change app/ or the entry scripts.sudo chown -R root:root app public, then give back the five SEO files.
No stray files in the webrootNo archives, database dumps, keys, logs, .git folders or phpinfo.php under public/.Move or delete the files it names. A release zip unpacked and left in the webroot is the usual cause.
Shipped code matches the release manifestEvery file of app/ and public/ equals the release (app/MANIFEST.sha256), no foreign PHP file sits next to them, and the manifest carries a valid release signature (app/MANIFEST.sig). Warns when the signature file is missing.See the list of files, copy the release again, and find out why if you did not change them. php app/cli.php security:manifest prints every difference. A bad signature means the manifest was rewritten: treat the server as tampered with.
Two-step sign-in for staffTwo-step sign-in is required for super admins and every active super admin has it; says how many workspaces require it from their members.Super → Security; see Super-admin sign-in and security.
Scheduler key strengthThe cron URL key has at least 32 random characters.Put a longer cron.key in data/config.php.
Outbound connection safeguardsCertificates of the payment providers are verified; webhook endpoints must be public https addresses.Remove the test-only settings it names from data/config.php.
data/ is closed to other system usersOther accounts on the server cannot list or read data/.sudo chmod o-rwx on the directories it names.
Client addresses are read correctlyRequests do not arrive through a proxy that the application does not know. Read from the request, so run it from this page.Add the proxy to http.trusted_proxies; see Hardening the server.
Private areas refuse anonymous requests (live)Through the web server: the workspace and platform areas answer with the sign-in page, the API with 401, the scheduler with 403 for a wrong key.The web server sends requests somewhere else than this install: compare the vhost with the shipped example.
Dispute evidence carries the wrapped-blobs guardOnly on installs with data/ inside the webroot.php app/cli.php evidence:wrap.
Platform apps and connected accountsNo set in service depends on a disabled platform application; every platform webhook endpoint refuses a forged signature. Warns for a verified application without its webhook value, for a connected set whose provider could not be asked three times in a row, and for an access token within five days of running out. Skipped when no platform application exists.Enable the application or disconnect the sets it names; add the webhook value; see Connected accounts.

System monitor#

System monitor shows the server's vitals — CPU, memory, swap, disks, open files, time sync, TLS certificate expiry, reboot needed, automatic updates — PHP and OPcache, MariaDB (buffer pool, connections, slow queries, temporary tables on disk, largest tables) and the application (queues, open checkouts, webhooks today). Recommendations turn findings into concrete settings and the exact commands to apply them. Critical findings are emailed to super admins at most every 6 hours.

External monitoring#

Point an uptime monitor at /health (/index.php?r=health on a plain vhost). It answers 200 {"status":"ok"} when the database, data directory and scheduler are fine, and 503 otherwise.