Troubleshooting
Logs
Under System → Logs you see the backend's newest 2000 log lines, live, with a level filter, search and a download as a text file. It needs the View logs permission (admins always have it), since logs can hold IP addresses, usernames and email addresses.
The lines live in memory, so they start over when the backend restarts. Older ones are still on the server:
docker compose logs backendHelp in the panel shows the state of your installation, with links to Discord, GitHub and Docker Hub.
A service shows as down with status 403, but it works in your browser
The site is probably behind Cloudflare or another firewall that blocks automated requests. AeroStat identifies itself as AeroStat/<version> (+https://github.com/Hampter-0/AeroStat), which most setups allow. If it is still blocked, add a rule in the firewall that lets your AeroStat server's IP address through.
A service is down only from AeroStat
Checks run from inside the backend container. Test from the same network with:
docker compose exec frontend wget -S -O /dev/null https://example.comLocked out of the panel
Everything below runs from the server with the command line:
| Problem | Command |
|---|---|
| Forgot the password | reset-password, or create-admin for an admin |
| Lost the authenticator app and recovery codes | reset-2fa |
| Lost the passkey, password sign-in is off | remove-passkeys or enable-password-login |
| Too many failed sign-ins | unblock |
| The account is suspended | unsuspend |
Every visitor has the same IP
AeroStat sees your proxy's address instead of the visitor's. Check the reverse proxy setup, and the Cloudflare part when you use Cloudflare.
Passkeys stopped working
A passkey only works on the domain it was made for. When the status page address under Settings → General changes, everyone has to add their passkeys again.
Everyone has to set up their authenticator app again
SECRET_KEY in .env changed or got lost. Put the old one back from your copy of .env, or let everyone set up their app again.