[GH-ISSUE #829] Nullify / unset default-user and default-password in client configuration? #583

Closed
opened 2026-05-07 00:25:36 +02:00 by BreizhHardware · 0 comments

Originally created by @tomeon on GitHub (Aug 2, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/829

Nullify / unset default-user and default-password in client configuration

First, thanks for ntfy -- it was easy to set up a self-hosted instance and has been a real treat to use.

I am using ntfy version 2.5.0 on NixOS 23.05. Here's my situation, slightly fictionalized for brevity and security:

--- 
# ~/.config/ntfy/client.yml

default-user: myuser
default-password: hunter2
default-host: https://ntfy.local # self-hosted, LAN-only
default-command: issue-desktop-notification

subscribe:
  - topic: thing
  - topic: other-thing
  - topic: yet-another-thing
  - topic: https://ntfy.sh/needs-to-use-public-host-for-reasons
    user: ??? # don't use `user` for public instance
    password: ??? # don't use `password` for public instance

My question is: what, if anything, can I use in place of the ???s above in order to disable authentication for the topic https://ntfy.sh/needs-to-use-public-host-for-reasons? I've tried using each of the four combinations in the Cartesian product of {"", null} x {"", null} for user and password, but none them work (which is to say that I continue to get 401s from ntfy sub --from-config).

Am I holding it wrong? Or is this not possible at present? I can of course list user and password for each of the subscriptions on my self-hosted instance, which is effective but cumbersome.

Thank you!

Originally created by @tomeon on GitHub (Aug 2, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/829 :question: **Nullify / unset `default-user` and `default-password` in client configuration** :question: First, thanks for `ntfy` -- it was easy to set up a self-hosted instance and has been a real treat to use. I am using `ntfy` version 2.5.0 on NixOS 23.05. Here's my situation, slightly fictionalized for brevity and security: ```yaml --- # ~/.config/ntfy/client.yml default-user: myuser default-password: hunter2 default-host: https://ntfy.local # self-hosted, LAN-only default-command: issue-desktop-notification subscribe: - topic: thing - topic: other-thing - topic: yet-another-thing - topic: https://ntfy.sh/needs-to-use-public-host-for-reasons user: ??? # don't use `user` for public instance password: ??? # don't use `password` for public instance ``` My question is: what, if anything, can I use in place of the `???`s above in order to disable authentication for the topic `https://ntfy.sh/needs-to-use-public-host-for-reasons`? I've tried using each of the four combinations in the Cartesian product of `{"", null} x {"", null}` for `user` and `password`, but none them work (which is to say that I continue to get `401`s from `ntfy sub --from-config`). Am I holding it wrong? Or is this not possible at present? I can of course list `user` and `password` for each of the subscriptions on my self-hosted instance, which is effective but cumbersome. Thank you!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#583
No description provided.