Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Security

SSL certificate expired: what to do before renewing blindly

Published August 2026 · 7 min read

When a certificate expires, the immediate goal is restoring a valid public TLS chain. The second goal is finding why renewal or deployment failed so the same outage does not recur at the next expiry.

Inspect the certificate the public server is actually presenting

Do not assume the file you renewed is the file the reverse proxy or web server uses. Check the public endpoint, hostname, issuer, serial, and expiry from outside the machine.

Review renewal logs and validation requirements

Automated certificate clients can fail because DNS or HTTP validation cannot reach the expected token, credentials expired, rate limits were hit, or the renewal job stopped running. Read the actual renewal result.

Reload services after successful deployment when required

Some services keep certificates in memory until configuration is reloaded. Confirm the process picked up the renewed certificate rather than leaving the old one active.

Add expiry monitoring independent of the renewal job

A cron job saying “success” is less useful than an external check of the certificate visitors receive. Alert far enough ahead of expiry to investigate safely.

Next step

An expired SSL/TLS certificate may indicate failed automation, DNS validation, wrong deployment path, stale proxy configuration, or a service no longer using the renewed certificate.

See hosting with HTTPS

Keep reading

Related guides.

Content Security Policy rollout: build CSP from the resources a site really uses

Inventory scripts, styles, frames and connections, start with reporting, reduce unsafe allowances and enforce CSP only after normal user paths still work.

Read the guide

HSTS rollout planning: enable strict HTTPS without locking in a mistake

Stabilize HTTPS first, choose max-age carefully, cover subdomains deliberately and understand preload consequences before making HSTS hard to reverse.

Read the guide

HTTPS redirect mistakes: loops, chains and host changes that hurt a site

Find conflicting HTTP-to-HTTPS and hostname redirects across proxies, servers and applications, then reduce the path to one intentional canonical destination.

Read the guide

More security guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move