Troubleshooting

Fixes for the problems you are most likely to hit with the Gotify Notification Server.

Sending a message is refused

Cause: the token is missing or wrong, or it is not an application token.

Fix: send an application token in the X-Gotify-Key header. Client tokens can read messages but cannot send them.

Reading messages with an application token returns 401

Cause: application tokens can only send.

Fix: create a client in the web UI and use its token for GET /message and the /stream WebSocket.

The admin password in the file does not work

Cause: the password was changed in the web UI. The file is used only when the database is first created.

Fix: use the password you set. Changing the file does not change the password.

The browser shows a certificate warning

Cause: the certificate is self-signed for this instance.

Fix: compare the fingerprint in your browser with openssl x509 -in /etc/gotify/tls/cert.pem -noout -sha256 -fingerprint on the instance. If they match, you can trust that certificate in your browser.

The phone app cannot connect

Cause: Gotify listens on 127.0.0.1 on the instance, which a phone cannot reach.

Fix: see Reach Gotify from other hosts.

First boot failed

Cause: sushi-gotify-firstboot.service failed, so Gotify did not start.

Fix: look at its log, then run it again and start Gotify:

sudo journalctl -u sushi-gotify-firstboot.service --no-pager
sudo systemctl restart sushi-gotify-firstboot
sudo systemctl start gotify

If it still fails, email info@softwaresushi.com with the instance ID and the log output.