Troubleshooting
Find the symptom, then follow the link to the page that explains the fix.
For a quick check, open Settings → System status. It shows whether the database answers, how much space is left on the data disk, whether the TAK server is listening, when its certificate expires and graphs of CPU and memory for the last six hours, and the warnings and errors of the last seven days. In Docker, CPU and memory are those of the container. Warnings and errors are kept in logs/problems.jsonl in the data directory, so they survive a restart or crash. The page needs the permission to read the server log.
Installation
| Symptom | Where to look |
|---|---|
| Core does not start | Run docker compose logs core. A port in use: TAK ports. A missing or doubled root key: Install. |
| The Web app is not reachable | Reverse proxy |
| Live server log only updates slowly | The proxy does not pass WebSocket upgrades: Reverse proxy |
| Password reset emails do not arrive | Email settings and test email: Configure the installation |
TAK apps
| Symptom | Where to look |
|---|---|
| No QR code on the dashboard | The TAK server needs a publicly trusted certificate: Server certificate |
| Enrollment fails | Port 8446 must be reachable: TAK ports |
| ATAK connects, but no Data Packages | TAK ports |
| iTAK cannot list Data Packages | TAK ports |
| Apps stopped connecting after a settings change | Devices keep the old address and ports: Changing ports later |
Participants
| Symptom | Where to look |
|---|---|
| A setup or access link does not work | Links work once and expire. Create a new one: Add members |
| The dashboard says "No active event" | The person is not a member yet, or the event is still a draft: Set up an event |
| A participant has no Meshtastic file | The event's Meshtastic configuration is not published yet: Meshtastic |
API
Every error response contains a traceId. Look it up under Settings → Server log. Status codes are explained in API basics.