SSL Certificate Error on Free Subdomain

Hosting Support
1

Website URL

https://www.allahordanbdshop.great-site.net/

Error Message

NET::ERR_CERT_COMMON_NAME_INVALID

Other Information

My website is hosted on InfinityFree.

The www version of my website opens, but the non-www version shows NET::ERR_CERT_COMMON_NAME_INVALID.

The SSL Certificates page says “No SSL certificates found”, although InfinityFree says free subdomains have SSL by default.

Please help me fix this SSL certificate issue.

2

Welcome to the InfinityFree community forum! Good to have you here.

  • Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
  • Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
  • AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
  • Solving an issue is a joint effort. Try the suggestions you get and report back what happened.
3

Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.

The error is on the www address, not the non-www one. The URL in your post is https://www.allahordanbdshop.great-site.net/. An article about free subdomain SSL says www is the part that can’t have SSL:

The system-wide SSL certificates can only protect direct subdomains, which means www subdomains are not covered. For example: the domain example.ct.ws is protected with SSL, but www.example.ct.ws cannot be protected.

So https://allahordanbdshop.great-site.net/ (no www) should be the one with a valid certificate. https://www.allahordanbdshop.great-site.net/ will show NET::ERR_CERT_COMMON_NAME_INVALID, and nothing on the hosting side can change that. The “No SSL certificates found” message on the SSL Certificates page is expected too. Free subdomains use the system-wide certificate, so nothing gets installed per account, and the article says waiting for it won’t change anything.

The fix is to use the non-www address as your website URL. The article suggests redirecting www to non-www, so old links still land on the right page. Redirecting from www can’t avoid the certificate warning on HTTPS, because the browser checks the certificate before it follows any redirect. The article also says you still need to set your website software’s URL to https:// and redirect all traffic to HTTPS.

Here’s the article:

If https://allahordanbdshop.great-site.net/ without www also shows the error for you, tell me exactly what the browser shows. Then it’s a different problem from this one.

4

The bot is absolutely correct. If I visit your site without “www.”, then SSL works just fine.

image
image334×218 8.96 KB

Sub-subdomains are not officially supported by InfinityFree, and that includes the WWW prefix.