SSL cert for incorrect site

[natetan]

I recently switched from using a write.as domain to using my own subdomain for a website I manage. Since I made the switch the SSL cert throws “NET::ERR_CERT_COMMON_NAME_INVALID” on Chromium and similar on Firefox.

• https://words.natestemen.xyz

Similar to Problem with SSL certificate it seems like my certificate is for 0x41.lol which is not my site.

[matt]

Hi @natetan, sorry for the delay on the certificate – you’re all set now!

It looks like in this case, the delay was due to the order everything was set up in. It would’ve resolved on its own eventually, but for future reference, here’s the best order to set up custom domains in:

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 se…