Troubleshooting¶

Container exits immediately¶

Inspect the logs first:

docker compose logs --tail=200 fritzfluxdb

Exit status 78 means the application rejected its configuration. Check DB_TYPE, the matching hostname, required database fields, port range, and TLS/plaintext credential settings. The watchdog does not retry status 78 because restarting cannot fix a static configuration error.

No measurements arrive¶

Check the following in order:

1. The FRITZ!Box host and credentials are correct and reachable from the container.
2. The database service name matches *_HOSTNAME on the Compose network.
3. The database, bucket, organization, or table permissions allow writes.
4. TLS settings match the endpoint and certificate trust.
5. The measurement/table name includes the sanitized FRITZ!Box serial when available.

Repeated backend warnings¶

The writer retries transient HTTP failures with backoff. Repeated warnings usually indicate reachability, TLS, authentication, or capacity problems. A 413 response is handled by shrinking the write batch; persistent failures can eventually fill the bounded buffer and drop oldest data.

Grafana shows no data¶

Confirm the datasource type and UID mapping, then use the actual serial-derived measurement name. The supplied dashboards do not invent data or query a fixed fritzbox name after a serial has been detected.

FRITZ!Box data is missing¶

Lua collection is disabled for FRITZ!OS versions below 7. Some services are model- or firmware- dependent. Look for service-specific warnings and compare the observed cadence with Polling and data model.