Skip to content

Troubleshooting

  • Docker Compose: docker compose ps shows healthy once Ingle answers on /healthz. The logs are in docker compose logs ingle.
  • Without Docker: systemctl status ingle, and the logs are in journalctl -u ingle.
  • Anywhere: /healthz answers ok and the version, for example ok v0.2.0, when Ingle and its database are working.

If Ingle stops straight after starting, the log says why. A bad setting names the variable, for example INGLE_TZ "London": unknown time zone London (it should be Europe/London).

Check that your Ingle address resolves to the server’s LAN IP: nslookup ingle.home.example.com. If it doesn’t, see the note on DNS rebinding protection in Install.

Run docker compose logs caddy (or journalctl -u caddy without Docker). The usual cause is a token without DNS edit permission on the right zone. Without Docker, check that caddy list-modules includes dns.providers.cloudflare.

Something between the iPad and Ingle is buffering the live updates at /board/events. See Reverse proxy.

“backup.failed … permission denied” in the logs

Section titled ““backup.failed … permission denied” in the logs”

The backup folder isn’t writable by Ingle.

Sign-in and unlocking stop working on every device

Section titled “Sign-in and unlocking stop working on every device”

After 20 wrong passwords, PINs or codes from one address, Ingle stops accepting them from that address for 5 minutes. Behind a proxy, if Ingle sees every device as the proxy’s address, one person’s mistakes lock out the whole house. Set INGLE_TRUSTED_PROXIES to your proxy’s address. See Reverse proxy.

If 172.30.40.0/24 is already used on your network, set INGLE_SUBNET and INGLE_PROXY_IP (an address inside it) in .env to another private range, then run docker compose down && docker compose up -d.

Admin › Calendars shows when each one last updated, and the error if the last try failed. Check that the server can reach the internet, and that the address is the secret iCal one, not the calendar’s web page.

The display was removed in Admin › Devices, or its browser’s cookies were cleared. Sign in on it and go to Admin › Devices › Make this a household display.