Where to find logs
The server and proxy write to the system journal. For details about an update error, check the app.
Server logs
Sign in to the server as root to read the journal.
| What you need | Command |
|---|---|
| Last 100 server entries | journalctl -u gadka -n 100 |
| Live server log | journalctl -u gadka -f |
| Entries from the past hour | journalctl -u gadka --since "1 hour ago" |
| Reverse proxy log (HTTPS) | journalctl -u gadka-proxy -n 100 |
The server writes one JSON entry per line.
Save logs to a file
To attach logs to a report, save them to a file:
journalctl -u gadka --since "1 hour ago" > gadka-log.txtReview the file before sending it. Logs can contain IP addresses and other details about your installation.
Get more detailed logs
In /etc/gadka/gadka.yaml, set the log level to debug:
log: { level: debug, format: json }Restart the server with sudo systemctl restart gadka, reproduce the problem, then set the level back to info.
Check server status
systemctl status gadka gadka-proxy
gadka healthcheck && echo OK
gadka --versionFor details and metrics, see Monitoring and logs.
Common log entries
| Entry | Meaning |
|---|---|
| A startup error naming a configuration key | The value in gadka.yaml is invalid. |
read secret: … | The server can’t read the secret file. Check its path, ownership (root:gadka), and permissions (0640). |
link safety: list update failed | The CERT Polska warning list is unreachable. |
LICENSE_SERVER_ID_CHANGED | The server machine has changed. See Changing servers. |
Information from the app
The app has no separate log window. When diagnosing a problem, collect the following details.
| Information | Where to find it |
|---|---|
| App version | Preferences, then About Gadka |
| Update error | Technical details in the Gadka updates window |
| Connection status | Look for Connecting…, Reconnecting…, or No connection. |
| Exact message | Copy the wording or take a screenshot. |