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

TLS certificate renewal: replace a certificate without an HTTPS outage

Published August 2026 · 2 min read · Updated 2026-09-05

TLS certificate renewal is an automated operational workflow: prove domain control, obtain a replacement, install it in the correct service, reload without breaking traffic, and verify the new certificate externally. The job is not finished because an ACME command printed “success.”

Know the validation method and dependency

HTTP-01 depends on public DNS and an accessible challenge path; DNS-01 depends on authoritative DNS automation; other methods have their own constraints. Record which account, credentials, and DNS/web path the renewal client uses.

A proxy or CDN can affect whether the challenge reaches the intended origin.

Renew before the emergency window

Run automated renewal checks regularly and alert well before expiry. Short-lived certificates are designed around reliable automation, not calendar reminders from a human.

Test renewal in staging where the CA supports it if you are changing the automation itself.

Install/reload every service using the certificate

Web servers, SMTP, IMAP, control panels, reverse proxies, and application gateways may use separate file paths or reload hooks. Inventory consumers so one service does not keep serving the old certificate after renewal.

Use config tests before reload when available.

Verify from outside

Check hostname, issuer, chain, expiry, and certificate fingerprint from an external connection after renewal. Keep logs for failed attempts and monitor days-to-expiry independently.

  • Document challenge method.
  • Alert before expiry.
  • Reload all certificate consumers.
  • Verify the served certificate externally.

Next step

Track expiry, automate renewal where appropriate, reload the serving process and verify the new chain externally before the old certificate becomes invalid.

See the DotMoose security approach

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