Blogger Custom Domain HTTPS: Why the Padlock Took Days, and the Switch That Took My Blogs Offline
I connected two Blogger blogs to my own subdomains on September 26, 2026. The blogs loaded over http:// within about 15 minutes of adding the DNS records. The padlock (https://) didn't show up that night, or the next day.
Here's what was actually wrong, the switch I flipped too early (which briefly took both blogs offline), a side effect that confused my publishing script, and the order I'd follow next time.
The timeline
| When (2026, local time) | What happened |
|---|---|
| Sep 26, 20:30 | Added the CNAME records at my domain registrar and saved the custom domains in Blogger |
| Sep 26, 20:44 | Both blogs loaded over http://. https:// failed to connect |
| Sep 27, ~21:15 | Found the cause in Blogger settings and turned on HTTPS availability |
| Sep 27, ~21:15 | Also turned on HTTPS redirect. Both blogs stopped loading for everyone. Turned redirect back off |
| Sep 30, 02:31 | Checked again: https:// loads on both blogs |
I didn't check between the evening of Sep 27 and early Sep 30, so I can only say the certificate appeared sometime within about 53 hours of turning availability on.
Photo: ed br on Pexels
Symptom: http works, https doesn't
After the custom domain was connected, http:// addresses returned the blog normally, but every https:// request failed at the connection stage. There was no certificate error to click through; the connection simply didn't complete.
Blogger's help page for custom domains mentions one known blocker: if your domain has CAA records, you must include one for letsencrypt.org, or Blogger can't create or renew the certificate (Blogger Help, checked 2026-09-26). I checked my DNS and had no CAA records at all, so that wasn't it.
The cause: HTTPS availability was off
In Blogger, go to Settings and scroll to HTTPS. There are two switches:
- HTTPS availability: whether your blog can be served over https at all. Mine said Status: No, and the switch was off.
- HTTPS redirect: whether visitors who arrive on http are sent to https. It was greyed out, because availability was off.
Once I turned availability on, the status changed to "Unknown," which in practice meant "working on it."
The mistake: turning on redirect too early
I turned on redirect at the same time, and it ended up on for both blogs. Blogger showed a warning that redirect won't work until HTTPS is activated. What actually happened in my test: every http:// request got a 301 redirect to https://, and https:// still didn't connect. For a few minutes, nobody could load either blog, including search engines.
Turning redirect back off restored access immediately.
The rule I use now: turn on availability, wait until an https:// address actually loads in your browser, and only then turn on redirect.
Photo: Google DeepMind on Pexels
A side effect I didn't expect
I publish through the Blogger API. After HTTPS availability was switched on, the API started returning post URLs as https://…, even though the certificate wasn't ready. My script checks each post by opening its URL right after publishing, so that check failed with a connection reset, although the post itself had been published fine.
I changed the script in two ways: it now records a post as published the moment Blogger creates it (so it can never post the same draft twice), and if the https address won't connect, it checks the http:// address instead.
Checklist
- ☐ Custom domain loads over
http://(DNS is done) - ☐ No CAA records, or one that allows
letsencrypt.org - ☐ Blogger Settings → HTTPS availability: on
- ☐ Wait until
https://yourdomainactually loads (for me: somewhere under ~53 hours) - ☐ Only then: HTTPS redirect on
- ☐ If you publish by API, don't assume the returned
https://URL works yet
Now that https loads on both my blogs, redirect is the last switch in that list, and it's finally safe to flip.
Comments
Post a Comment