[GH-ISSUE #1292] All notifications broken whenever one is unauthorized #914

New issue

Closed

opened 2026-05-07 00:28:43 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:28:43 +02:00

Owner

Originally created by @tobast on GitHub (Mar 13, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1292

🐞 Describe the bug

Whenever one subscription on the Android app is unauthorized server-side, all subscriptions for this server stop working (as a single connection is established). This is also true of UnifiedPush subscriptions, that are auto-created without prompting the user to grant rights.

I noticed this problem after starting FluffyChat: this created a UnifiedPush subscription in ntfy through a new channel; however, my server has a default-deny ACL policy. This made ntfy-android unable to connect to ntfy, as one of the required subscriptions was denied; which means that all other subscriptions broke in the meantime.

A possible solution to this issue would be to detect subscription errors to some channels, and re-initiate a connection minus the denied channels, while notifying the user locally of the error.

💻 Components impacted

Android app

💡 Screenshots and/or logs

Can provide if necessary.

🔮 Additional context

Originally created by @tobast on GitHub (Mar 13, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1292 :lady_beetle: **Describe the bug** Whenever one subscription on the Android app is unauthorized server-side, all subscriptions for this server stop working (as a single connection is established). This is also true of UnifiedPush subscriptions, that are auto-created without prompting the user to grant rights. I noticed this problem after starting FluffyChat: this created a UnifiedPush subscription in ntfy through a new channel; however, my server has a default-deny ACL policy. This made ntfy-android unable to connect to ntfy, as one of the required subscriptions was denied; which means that all other subscriptions broke in the meantime. A possible solution to this issue would be to detect subscription errors to some channels, and re-initiate a connection minus the denied channels, while notifying the user locally of the error. :computer: **Components impacted** Android app :bulb: **Screenshots and/or logs** Can provide if necessary. :crystal_ball: **Additional context**

BreizhHardware

2026-05-07 00:28:43 +02:00

closed this issue
added the
🪲 bug
label

BreizhHardware commented

2026-05-07 00:28:43 +02:00

Author

Owner

@tobast commented on GitHub (Mar 13, 2025):

Somewhat related to #991

@tobast commented on GitHub (Mar 13, 2025): Somewhat related to #991

BreizhHardware commented

2026-05-07 00:28:44 +02:00

Author

Owner

@binwiederhier commented on GitHub (Jan 20, 2026):

This is now easier to diagnose with the Connection error dialog in the 1.22.x release. Thanks for reporting.

@binwiederhier commented on GitHub (Jan 20, 2026): This is now easier to diagnose with the Connection error dialog in the 1.22.x release. Thanks for reporting.

BreizhHardware referenced this issue

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

[PR #917] [MERGED] user.Manager: fix ACL write, read order #1462