Guide: When something is not working

The checks that resolve most reports, in the order worth trying.

About 5 minutes.

1. Check the health panel first It reports HTTPS, PHP extensions, the API admin account and the notification keys. Most problems are one of those four being unset.
2. Nobody can sign in Look for auth.login entries marked failed. A blank API admin account produces a 503 rather than a wrong-password error, which is the usual cause right after install.
3. Notifications stopped for one person Their device row will show as inactive: the push service returned 404 or 410, meaning the browser discarded the subscription. They turn notifications on again and a new row appears.
4. Notifications stopped for everyone Almost always regenerated VAPID keys. The delivery log will show 403 responses across every device.
5. The app shows an old version The service worker caches the shell. Bumping the module version changes the cache name and clears it on next launch, so upgrading is usually the fix.