Repository navigation
Self hosted servers
NtfyBar works with ntfy.sh and with your own ntfy server. You can add several servers.
Settings › Servers, add the server URL, pick how to sign in, then choose that server in a topic.
| Sign-in | Use for |
|---|---|
| None | open topics |
| Username and password | servers with user accounts |
| Access token | token auth (a tk_… token) |
Credentials are stored in config.json in ~/Library/Application Support/NtfyBar/ (folder readable only by you, file mode 600).
For how to set up users and tokens on the server, see the ntfy docs: Access control and Publishing with a token.
NtfyBar does not follow redirects. If your server redirects (for example http to https, or a reverse proxy), enter the final URL, for example https://ntfy.example.com. See "Server redirects" in Troubleshooting.
Settings warns you when a server uses plain http together with credentials: they travel unencrypted. Use https on anything but a trusted network.
For a server such as http://192.168.1.5:8080, macOS asks for Local Network permission the first time. Allow it. If you denied it, enable it in System Settings › Privacy & Security › Local Network.
curl -H "Authorization: Bearer <your token>" -d "Hello" https://ntfy.example.com/<your topic>After sleep or offline time, NtfyBar asks the server for messages since the last one it saw. It can only get what the server still has cached (12 hours on ntfy.sh; your own server sets its own cache duration, see the config docs).
