dearsky/ntfy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add troubleshooting steps for "Reconnecting" error on mobile

Browse Source
This commit is contained in:
Pixelguin
2026-01-05 08:11:20 -08:00
parent e18d64933f
commit 39936a95f8
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/troubleshooting.md
View File

@@ -129,3 +129,14 @@ keyboard.
## iOS app ## iOS app
Sorry, there is no way to debug or get the logs from the iOS app (yet), outside of running the app in Xcode. Sorry, there is no way to debug or get the logs from the iOS app (yet), outside of running the app in Xcode.
## Other
### "Reconnecting..." / Late notifications on mobile (self-hosted)
If all of your topics are showing as "Reconnecting" and notifications are taking a long time (30+ minutes) to come in, or if you're only getting new pushes with a manual refresh, double-check your configuration:
* If ntfy is behind a reverse proxy, make sure `behind_proxy` is enabled.
* If ntfy is behind Nginx, make sure WebSockets are enabled.
* Make sure you have granted permission to access all of your topics, either to a logged-in user account or to `everyone`. All subscribed topics are joined into a single WebSocket/JSON, so a single topic that receives `403 Forbidden` will prevent the entire request from going through.
* In particular, double-check that your user has permission to read `up*` if you are using UnifiedPush.