Docs: show the admin socket startup warning instead of a CLI message that does not exist

This commit is contained in:
binwiederhier committed 2026-10-31 00:44:26 +00:00
1 parent a2656890d1
commit 84861a015c
1 file changed
+3 -4
+3 -4
View File
@@ -925,12 +925,11 @@ mode `0660` in a directory with mode `0750`, both owned by the user ntfy runs as
and `root` can use it. With the Debian/Ubuntu/Fedora packages, the shipped systemd unit creates `/run/ntfy` (via
`RuntimeDirectory=ntfy`), so `sudo ntfy user add ...` and members of the `ntfy` group just work.
The socket is only opened if [access control](#access-control) is configured (`auth-file` or `database-url`). If no
server answers on the socket (the server is not running, or it cannot create the socket), the commands fall back to
writing to the database directly, like they did before, and print a warning:
The socket is only opened if [access control](#access-control) is configured (`auth-file` or `database-url`). If the
server cannot create the socket, it logs a warning at startup and runs without it:
```
warning: ntfy server not reachable at /run/ntfy/admin.sock, writing to the database directly; a running server picks this up within 1m27s
WARN Admin socket /run/ntfy/admin.sock not available, 'ntfy user/access/token/tier' will write to the database directly, which is deprecated, see https://ntfy.sh/docs/deprecations/ (error=mkdir /run/ntfy: permission denied, tag=startup)
```
To change the path, set `listen-admin-unix` in the `server.yml` file; the commands read it from there, too. To disable the