--- url: https://docs.codefox.ai/self-host/health.md --- # Check the server's health This page lets you find out whether the server and its apps are working, read their logs, and gather what someone helping you needs. ## In Admin * **Home** shows the server's processors, memory and disk, and lists what **Needs your attention**, most urgent first. Each row opens the page that fixes it. * **Server** › **System** runs the server's own check of itself under **Health check**: ports, disk, DNS, mail and each app's settings. What needs you comes first, each with what was seen and what to do; **Good to know** holds reminders that are not problems. * **Server** › **Products** shows each app's version, whether it answers, and under **To finish** what each app still needs before everything works. * **Server** › **Backups** shows each app's newest backup and whether its off-site copy arrived. ## With the CLI ### One verdict: checkup Run `foxden checkup`. It runs the server check, the status of each app, an email deliverability check and a test that the newest backup restores, then gives one verdict: | Verdict | Exit code | Meaning | |---|---|---| | **fit** | 0 | Everything checks out. | | **running, but** | 1 | The apps run, and something needs your attention. The reason follows. | | **not ready** | 3 | The server is not ready: nothing is installed, or something it needs is missing. | Run it once a week, and whenever something feels wrong. ### Every check: doctor `foxden doctor` runs each check on its own and prints, for each one, what it saw and the fix. Narrow it down: * `foxden doctor --product fennec`: one app's checks (the server-wide checks always run). * `foxden doctor --fail-only`: only warnings and failures, with their fixes. * `foxden doctor --check backup-fresh`: one check by its name. * `foxden doctor --domain example.com`: also check that the domain points at this server. Each line starts with the check's name, such as `health`, `sizing`, `dns`, `backup-fresh` or `email-spf`. The messages, and what to do about each, are on [Fix server problems](/self-host/troubleshoot). ### What is running: status `foxden status --product fennec` lists the app's containers, the image each runs, its version and whether it is healthy. `foxden status --watch` redraws it every 2 seconds until you press q. ### Logs `foxden logs` asks which service to read, then whether to follow it, show errors, or search. Or say it in one line: * `foxden logs app --follow --product fennec`: follow the app live; Ctrl-C stops. * `foxden logs --errors --product fennec`: errors from every service of the app. * `foxden logs app --since 1h`: the last hour. * `foxden logs --grep timeout -C 3`: every line with "timeout", three lines either side. * `foxden logs caddy --product arctic`: the web server of Arctic installed on its own, where certificate errors show. Each app's services are named in its compose file: usually `app`, `worker`, `db`, `migrate` and `updater`. Each app's page lists its own, for example [Running Fennec](/self-host/running-fennec). The shared web server in front of the apps is not part of any app, so `foxden logs` does not read it. On the server, run `docker compose --project-directory /opt/foxden/ingress logs caddy` to see its certificate errors. Backups log to `/var/log/-backup.log` on the server (for Fennec, `/var/log/codefox-crm-backup.log`), and the weekly restore test to `/var/log/-restore-verify.log`. ### A file for a support thread `foxden support-bundle --product fennec` writes one file, `foxden-support-fennec-