Why isn't my SSL certificate issuing?
Nearly always, it's because the domain isn't pointing at TDesk yet.
TDesk runs a pre-flight DNS check and deliberately won't attempt a Let's Encrypt certificate until the domain resolves to us - this protects you from burning a Let's Encrypt rate limit on a zone that isn't ready.
To fix it: 1. Confirm the domain's nameservers (or A record) point at TDesk. 2. Allow DNS to propagate (usually minutes, occasionally up to a few hours). 3. The panel retries automatically - no need to re-add the domain.
If it still hasn't issued after DNS is clearly pointing at us, raise it here and we'll take a look.

0 comments
Sign in with your TDesk account to comment.