[GH-ISSUE #1375] Battery Optimization When App Sync is Blocked by VPN or Firewall #974

New issue

Closed

opened 2026-05-07 00:29:16 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:29:16 +02:00

Owner

Originally created by @ulairii on GitHub (Jun 29, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1375

❓ Question

Hi,

I’ve encountered an issue when using ntfy with a VPN connection. When the VPN blocks ntfy’s internet access, the app still continuously attempts to sync in the background.

Although I assume there may already be some retry or backoff mechanisms in place, the repeated sync attempts while the server is unreachable can lead to unnecessary battery consumption.

Would it be possible to add a customized, app-level server reachability check before starting synchronization? This could help prevent redundant sync attempts when the app is effectively blocked by the VPN.

Here are some references that may help:

StackOverflow: Server reachability check

DAVx⁵ solution for handling VPN-related sync issues

Thank you!

Originally created by @ulairii on GitHub (Jun 29, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1375  :question: **Question**  Hi, I’ve encountered an issue when using ntfy with a VPN connection. When the VPN blocks ntfy’s internet access, the app still continuously attempts to sync in the background. Although I assume there may already be some retry or backoff mechanisms in place, the repeated sync attempts while the server is unreachable can lead to unnecessary battery consumption. Would it be possible to add a customized, app-level server reachability check before starting synchronization? This could help prevent redundant sync attempts when the app is effectively blocked by the VPN. Here are some references that may help: [StackOverflow: Server reachability check](https://stackoverflow.com/a/4009133/18154447) [DAVx⁵ solution for handling VPN-related sync issues](https://github.com/bitfireAT/davx5-ose/commit/318939e970297e9d491b82cbe5238adea82fd969) Thank you!

BreizhHardware

2026-05-07 00:29:16 +02:00

closed this issue
added the
question
label

BreizhHardware commented

2026-05-07 00:29:17 +02:00

Author

Owner

@binwiederhier commented on GitHub (Feb 1, 2026):

The retry is only every 2 minutes, so it shouldn't bleed the battery. I also added a "connection error dialog" recently that should make it more obvious that it's blocked/unreachable.

@binwiederhier commented on GitHub (Feb 1, 2026): The retry is only every 2 minutes, so it shouldn't bleed the battery. I also added a "connection error dialog" recently that should make it more obvious that it's blocked/unreachable.