Browse Source

Merge pull request #1534 from Pixelguin/feat/ws-permissions-note

Add troubleshooting steps for "Reconnecting" error on mobile
Philipp C. Heckel 1 month ago
parent
commit
9135bb277b
1 changed files with 12 additions and 0 deletions
  1. 12 0
      docs/troubleshooting.md

+ 12 - 0
docs/troubleshooting.md

@@ -129,3 +129,15 @@ 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 (such as Nginx):
+  * Make sure `behind_proxy` is enabled in ntfy's config.
+  * Make sure WebSockets are enabled in the reverse proxy config.
+* 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 request, so a single topic that receives `403 Forbidden` will prevent the entire request from going through.
+  * In particular, double-check that `everyone` has permission to write to `up*` and your user has permission to read `up*` if you are using UnifiedPush.