mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-10 00:08:52 +02:00
[GH-ISSUE #1282] 403 when requesting designated topics when auth deny-all is used #909
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#909
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 @elyashivhazan on GitHub (Feb 23, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1282
🐞 Describe the bug
When enabling auth with deny-all the Public/designated topics dont work, when using a real user (not admin) the server is responding with 403, with a made up user the server is responding with 401.
The server should respond with 401 for unauthorized users but respond with true (json) when authorized.
💻 Components impacted
Using the designated topics
💡 Screenshots and/or logs
🔮 Additional context
Could be related to #1018 because i found that issue when trying to use this app
i have solved this issue by running:
i hope this could be solved, honestly i have no idea if its on purpose (if it is pleases mention in the docs)
if you need more info i will gladly provide
@wunter8 commented on GitHub (Feb 24, 2025):
I'm not exactly sure what you mean. Are you referring to the topics
statsandannouncementson a self-hosted instance? They don't exist by default. They are special topics on the ntfy.sh instance, but they aren't included on self-hosted instances/nothing is posted automatically to those topics on a self-hosted instance.So, if you want people to be able to access those topics on your server, and you have default access set to
deny-all, you'll need to allowread-onlyaccess to those topics like you did above@elyashivhazan commented on GitHub (Feb 24, 2025):
Hi, i didnt except for messages to be sent automatically but to behave as in the main server because some apps using them as checks with them.
I guess its the app problem so im going to close this issue.
I think it should be mentioned in the docs.
have a nice day