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.
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: