SSL troubleshooting

Common SSL issues and how to fix them.

"SSL certificate could not be issued"

Almost always means DNS hasn't propagated yet. Let's Encrypt needs to confirm you control the domain by checking DNS. If your nameservers aren't pointing at TDesk yet, the verification fails.

Fix: confirm at your registrar that NS records point at ns1/ns2/ns3.tdesk.uk. Wait 1-4 hours for propagation. Then re-run the SSL job from the Domain detail page.

"Rate limit exceeded"

Let's Encrypt limits attempts to 5 failed validations per hostname per hour. If you've been retrying, wait an hour before trying again.

Browser shows certificate warning

If the browser shows "Not secure" or a warning page, check:

• Is the cert actually issued? Check the SSL tab
• Is your DNS pointing at the right IP?
• Are you on a network with a transparent HTTPS proxy (some corporate networks)?
• Has the cert recently been renewed but your browser cached the old one? Hard refresh.

Certificate expired

Should never happen — auto-renewal runs 30 days before expiry. If it does, the renewal job will be in failed state on the Jobs page. Click into it to see why and retry. Common cause: DNS changed after the cert was originally issued.