SiroPing
Open App
Community · Pro · Business

Troubleshooting

Quick diagnostics for the most common SiroPing problems.

Troubleshooting

Start with Doctor — it localizes most faults:

sudo -u siroping /opt/siroping/venv/bin/python /opt/siroping/manage.py doctor

Common issues

No alerts are arriving

  • doctorSMTP/Telegram/Webhook status.
  • Did you send a Test notification from each channel?
  • Email: check SPF/DKIM on your relay; check the server IP isn't blocked.

Monitor stuck "Unknown"

  • doctorScheduler/Worker freshness.
  • Is siroping-worker + siroping-beat running and Redis up?
systemctl status siroping-worker siroping-beat redis-server
journalctl -u siroping-worker -f

Status page 404

  • Is the project's status page enabled and the slug correct?
  • Does your plan include status pages? (Pro/Business)

Monthly report blocked

  • Does your plan include monthly reports? Check with:
python manage.py licensing_info

Cannot create a 6th monitor

  • Community limit = 5. Upgrade with a Pro/Business license (see Licensing).

Security warning in Doctor

  • DEBUG off? Strong SECRET_KEY? ENCRYPTION_KEY set? HTTPS + secure cookies?

Login blocked ("try again in 15 minutes")

  • That's the login rate-limit after 5 failed attempts per IP+user. Wait it out; a successful login resets it.

Logs

Log Path
App log /opt/siroping/logs/app.log
Playwright (login-form checks) /opt/siroping/logs/playwright.log
Worker journalctl -u siroping-worker -f
Web journalctl -u siroping-web -f

Still stuck?

  • Run doctor --json and share the checks.
  • Include the relevant journalctl lines and app log tail in any support request.
Was this page helpful?