Ver Fonte

Add troubleshooting steps for "Reconnecting" error on mobile

Pixelguin há 1 mês atrás
pai
commit
39936a95f8
1 ficheiros alterados com 11 adições e 0 exclusões
  1. 11 0
      docs/troubleshooting.md

+ 11 - 0
docs/troubleshooting.md

@@ -129,3 +129,14 @@ keyboard.
 
 ## 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.
+
+## 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.