Problem with SSL certificate

Thanks, please do.

Besides the starting topic of this thread, most of these issues are likely caused by certificates just taking a bit to generate. We have an automated process that, once you set a custom domain as your blog’s Preferred URL, checks that the domain is correctly pointed at our server and requests an SSL certificate via Let’s Encrypt.

A few things can slow this down:

  • The automated process pinging the domain before DNS settings have fully propagated
  • The same for Let’s Encrypt servers
  • If a domain name is brand new (DNS settings take even longer to propagate)

To ensure certificates are generated as quickly as possible, be sure to set things up in the order mentioned on the Help page. Specifically:

  1. First, set DNS settings
  2. Wait at least 30 minutes for settings to propagate (or longer, if your TTL is a large value)
  3. Finally, set the Preferred URL on Write.as

This should avoid many DNS-related delays.

Either way, the certificate process works without a hiccup most of the time. And it does automatically track when a certificate has been successfully generated, so people will automatically be redirected from the insecure site to secure when it’s ready – no work needed on your part. In most cases, setting everything and letting the robots do their thing should mean your site is up and secure in no more than 24 hours. But again, if you still notice an issue, please mention it!

2 Likes