Initial Setup
- Platform 2040 brings the app up on HTTP first so ACME validation can succeed.
- Certbot runs after nginx is answering on port `80` for the exact domain.
- If issuance succeeds, nginx is switched to the HTTPS config.
Certbot + SSL
Log in to inspect Platform 2040 SSL and certificate workflow details.
How Certbot + SSL Works On Platform 2040
Quick reference for how Platform 2040 handles certificate issuance, renewal, and the failure cases that matter.
Renewal
- Renewal is scheduled by Platform 2040 and enqueued into the same worker as new certificate issuance.
- Certificates live under `/etc/letsencrypt/live/<domain>/`.
- Nginx site config lives at `/etc/nginx/sites-available/<domain>.conf`.
Recent Counters
Loading recent Certbot activity…
Platform 2040 Behavior
All issue and renew requests are persisted as SSL jobs and executed by one Platform 2040 worker. If a create flow reaches the SSL step while another SSL job is already running, the new job stays queued and the app can remain in SSL pending until the queued job completes.
This page shows queue-backed SSL job activity from Platform 2040 itself, not systemd Certbot timer activity.
Quick Checks
Useful checks:
dig +short <domain> A
sudo nginx -t
ls -la /etc/letsencrypt/live/<domain>
curl -I https://<domain>
echo | openssl s_client -connect <domain>:443 -servername <domain> 2>/dev/null | openssl x509 -noout -subject -issuer -dates -ext subjectAltName
Recent Timeline
Loading recent Certbot runs…
Waiting for timeline data…