My site worked a week ago, and suddenly is broken: "Can’t Provide a Secure Connection"

[happydylansmith]

My site (https://www.nbatop80.com) that worked a week ago, and suddenly it's broken.

I'm a novel at this and am very lost. Any ideas on how to troubleshoot would be so so appreciated.

All of a sudden, today when I visit the site, I see the error "This site can’t provide a secure connection. www.nbatop80.com sent an invalid response. ERR_SSL_PROTOCOL_ERROR" or "Suspicious Site Blocked".

The domain name is through Blue Host, and I'm using the following DNS settings (where what is blacked out is mygithubname.github.io (again, this all worked perfectly a week ago).

On Github's page settings, I've included the custom domain and Enforced HTTPS.

[divyanshsood22]

This usually happens when GitHub Pages can’t issue or renew the SSL certificate for your custom domain.

First check these things then move to next para:

• Your root domain (nbatop80.com) should use A records, not a CNAME. It should point to GitHub’s IPs
• Only www.nbatop80.com should be a CNAME pointing to happydylansmith.github.io

After this, you can try doing these things:

• Remove and re-add the custom domain in Repo -> Settings -> Pages
• Re-enable Enforce HTTPS
• Wait 30–60 minutes for SSL/DNS to settle

[happydylansmith]

thank you so much for your answer! I updated the DNS settings, it seems to have solved the issue for now!

[happydylansmith]

Unfortunately it seems to be broken again. I'm getting this error:

[mecodeatlas]

Hi @happydylansmith!
I just tested your site from my side and it loaded normally over HTTPS, with no security warnings.

Is it still showing an error for you?

[happydylansmith]

Yes, it seems to be working now! Thanks so much for checking it out and helping!!

[happydylansmith]

Unfortunately it seems to be broken again. I'm getting this error:

[edenallen7]

The ERR_SSL_PROTOCOL_ERROR / “Suspicious Site Blocked” usually means your HTTPS/SSL setup no longer matches your DNS. In Bluehost, make sure www.nbatop80.com is only a CNAME pointing to yourgithubname.github.io (no extra A/AAAA records). On GitHub Pages, keep the custom domain + “Enforce HTTPS” enabled, then clear your browser/DNS cache and give it some time for the new certificate to re‑provision.

This resource might help too - https://certera.com/blog/how-to-fix-err-ssl-protocol-error-in-chrome/