Simulate a backend outage
Run this only during an agreed maintenance window: it interrupts media API requests. Keep a second SSH session available to restart the service.
bash
sudo systemctl stop ownmediahostCheck the backend-facing /health URL and wait for the monitor to record the failure. A 3-minute check interval does not guarantee an alert within exactly 3 minutes.
bash
curl -i https://media.yourdomain.com/healthRestart the backend and confirm that the service is healthy:
bash
sudo systemctl start ownmediahost
sudo systemctl status ownmediahost
curl -i https://media.yourdomain.com/health/readyVerify recovery on the next monitoring checks and review the recorded incident duration.
Test connectivity
bash
sudo bash /opt/ownmediahost/scripts/connect-status.sh --testDisconnect the status page
Unlinks OwnMediaHost from the configured status page; manage the external monitor separately in Better Stack.
bash
sudo bash /opt/ownmediahost/scripts/connect-status.sh --disconnectTroubleshooting
| Symptom | Check |
|---|---|
| Dashboard works, API fails | Service status and backend journal |
| No incident when backend stops | Ensure the monitor targets /health, not / |
| Database failure is not detected | Add readiness or response-content checks |
| Status domain has no certificate | DNS target and DNS-only mode |
| Browser probe fails | Health URL, HTTPS, CORS, and configured origins |
bash
sudo journalctl -u ownmediahost -f
sudo systemctl status caddy