Security & uptime
Downtime / SSL / cron
Outages, expiring certificate or domain, or sudden Watch score drop — Guard and Health.
Typical symptom
Guard alert email, SSL in 14 days, occasional 503, Explorer watch_score_drop.
Puluno modules
GuardHealth
Undo change
No — info / hosting only
Issue codes
http_down, ssl_expiring, domain_expiring, watch_score_drop
What you see
- Finding
http_down— homepage not returning 200. ssl_expiring/domain_expiring— expiry approaching.watch_score_drop— Watch score dropped by X points.- Client: “Worked yesterday, white screen today.”
Why it happens
Uptime and certificates are operations, not on-page SEO.
Common causes:
- Expired Let's Encrypt without auto-renew (server cron).
- Domain not renewed at registrar.
- PHP fatal after update (see After WP update).
- Host maintenance / DDoS.
- Cron not running → mail queue / full disk → 503.
What Puluno does
| Phase | Module | Action |
|---|---|---|
| Diagnose | Guard | uptime, SSL, domain |
| Diagnose | Explorer Watch | score and finding diff |
| Apply | — | Puluno does not fix the server |
| Verify | Guard + Explorer | 200 OK, stable score |
Guard watches — it does not replace hosting support.
Step by step
- Guard dashboard — which check failed (HTTP / SSL / domain).
- curl homepage from external network — confirm outside office.
- SSL: certbot / host panel — renew + nginx reload.
- Domain: renew at registrar, WHOIS contact current.
- 503: PHP error log, disk space, cron (WP-Cron).
- Verify: Guard green + Explorer after stabilization.
Rollback — undo the change
Uptime incidents have no Puluno rollback.
After SSL/domain fix, Verify monitoring only.
When it is not Puluno
- Client DNS wrong after migration — registrar.
- Cloudflare “Development mode” left on — CF settings.
- Score dropped due to new SEO finding, not outage — different playbook.
Related situations
Module manual