mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #1632] Cannot grant permissions to display desktop notifications #1138
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#1138
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wsw70 on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1632
🐞 Describe the bug
When opening Ntfy on a browser, I cannot grant permissions to display notifications. I keep clicking on the button (see below), the button ripples and that's all.
💻 Components impacted
Web app (Chrome 145 and a few before, I think)
💡 Screenshots and/or logs
There are no interesting logs in the browser console.
@binwiederhier commented on GitHub (Mar 8, 2026):
Thanks for the GIF :-) Are you running this on HTTPS or HTTP. The Notifications API is only supported on HTTPS.
Does it work on ntfy.sh?
@wsw70 commented on GitHub (Mar 9, 2026):
Ahhhh, I found the "issue". I don't know how I missed the fact that notifications were blocked for ntfy:
When I "allow for this site" everything is fine.
Now, I have a tiny concern still: ntfy is the only site (ntfy.sh or self-hosted) where I get this behaviour. The request for notifications is allowed globally:
I see this exclusively on Chrome, Firefox behaves as intended.
This is to say that maybe, maybe, ntfy is asking for the permission in a slightly unconventional way, which on Chrome appears as a blocked request that requires a manual fix.
It may be me only, and in any case it is a low-interest issue but it may be worthwhile to keep in in a corner of the mind if the issue is raised again.