Troubleshooting¶

Fixes for the problems you are most likely to hit with the Gatus Status Page.

The page loads but shows no status data¶

Cause: the status data needs the admin credentials.

Fix: sign in as admin with the password from sudo cat /var/lib/gatus/admin.password. If you changed the hash in config.yaml, use the password you set.

Gatus does not start after a config change¶

Cause: usually a YAML error in /etc/gatus/config.yaml.

Fix: read the error, fix the file and restart:

sudo journalctl -u gatus -n 50 --no-pager
sudo systemctl restart gatus

The browser shows a certificate warning¶

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

Fix: compare the fingerprint in your browser with sudo openssl x509 -in /var/lib/gatus/tls/cert.pem -noout -sha256 -fingerprint on the instance. Do not turn off TLS verification elsewhere to work around it.

An endpoint is always down¶

Cause: the instance cannot reach the target, or the condition does not match the response.

Fix: test the target from the instance, for example curl -I https://<your-site>/. Check the VPC routes, security group egress rules and DNS, and check that the conditions match what the target returns.

First boot failed¶

Cause: sushi-gatus-firstboot.service failed, so Gatus did not start.

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

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

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