[GH-ISSUE #299] docs: clarify what happens when it fails to connect to upstream base url #232

New issue

Closed

opened 2026-05-07 00:21:52 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:21:52 +02:00

Owner

Originally created by @prabirshrestha on GitHub (Jun 1, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/299

What happens if upstream-base-url is set but fails to send to the upstream server. This could be due to temporary internet connection issue or upstream server in maintenance mode. Will this be retried or will be lost?

Originally created by @prabirshrestha on GitHub (Jun 1, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/299 What happens if upstream-base-url is set but fails to send to the upstream server. This could be due to temporary internet connection issue or upstream server in maintenance mode. Will this be retried or will be lost?

BreizhHardware

2026-05-07 00:21:52 +02:00

closed this issue
added the
question

ios
labels

BreizhHardware commented

2026-05-07 00:21:53 +02:00

Author

Owner

@binwiederhier commented on GitHub (Jun 1, 2022):

Thanks for this question!

The docs already say this:

If upstream-base-url is not set, notifications will still eventually get to your device, but delivery can take hours,
depending on the state of the phone. If you are using your phone, it shouldn't take more than 20-30 minutes though.

This is facilitated by the ~poll topic, which all iOS devices subscribe to. The server sends a keepalive message to the iOS app every 20 minutes, which triggers it to poll all subscriptions. This is the only way on iOS to run scheduled code. Otherwise I would have used a timer for that.

I think the docs are sufficient for this. The implementation details are not that important and may change. I'm closing this for now.

@binwiederhier commented on GitHub (Jun 1, 2022): Thanks for this question! The docs [already say this](https://ntfy.sh/docs/config/#ios-instant-notifications): > If `upstream-base-url` is not set, notifications will still eventually get to your device, but delivery can take hours, depending on the state of the phone. If you are using your phone, it shouldn't take more than 20-30 minutes though. This is facilitated by the `~poll` topic, which all iOS devices subscribe to. The server sends a keepalive message to the iOS app every 20 minutes, which triggers it to poll all subscriptions. This is the only way on iOS to run scheduled code. Otherwise I would have used a timer for that. I think the docs are sufficient for this. The implementation details are not that important and may change. I'm closing this for now.

BreizhHardware referenced this issue

2026-05-07 01:01:11 +02:00

[PR #232] [MERGED] WIP: Accessibility of web app #1245