SSL Help

[belenn]

hello why do I get this : The certificate is not trusted in all web browsers. You may need to install an Intermediate/chain certificate to link it to a trusted root certificate. Learn more about this error. The fastest way to fix this problem is to contact your SSL provider. help mee

[Greenreader9]

What is your domain name?

Because of the way our system works, some automatic scriptes used to check your site give false information.

[KangJL]

@belenn

The certificate is not trusted in all web browsers.

Read this

Warning: "The certificate is not trusted in all web browsers"

If you have installed an SSL certificate on InfinityFree, you may want to use an SSL Checker tool to verify your SSL certificate was installed correctly. However, when doing so, you see an error like this: The certificate is not trusted in all web browsers. You may need to install an Intermediate/chain certificate to link it to a trusted root certificate. Learn more about this error. The fastest way to fix this problem is to contact your SSL provider. What does this warning mean for your sit…

[anon3276028]

@belenn welcome to the community.

It happens when you are installing a GoGetSSL or, ZeroSSL in your free subdomains. But installing LetsEncrypt have no problems like this. I think this is not a problem of free plan, it’s a problem of ssl providers.

@Admin

Because recently I installed LetsEncrypt ssl in my subdomain and I didn’t face this type of problem, but when I install ZeroSSL or GoGetSSL, the error happens.

Let's encrypt is use able to subdomains also!

Website URL- https://nope-dns.html-5.me In this new beta update of ssl certificate page, I was able to issue a let’s encrypt ssl certificate for my subdomain, and it worked, so why you said that let’s encrypt is not for subdomains. This worked so well, my website is very much secured, trusted, and smoothly working. No problems. You should take care of your free subdomain users. But let’s encrypt ssl should not be available for free subdomains, because free subdomains are mostly used for fraud…

[KangJL]

@anon3276028

Because recently I installed LetsEncrypt ssl in my subdomain and I didn’t face this type of problem, but when I install ZeroSSL or GoGetSSL, the error happens.

Did you read??

@Admin

The reason Let’s Encrypt doesn’t work for subdomains is that Let’s Encrypt has limits on how many certificates they will issue for a certain registered domain name. That limit is 50 certificates per week right now.

So that means that Let’s Encrypt will only provide 50 certificates per week for html-5.me and ALL subdomains. And if you look at how many certificates we issue for, say, epizy.com , 50 per week is nowhere near enough to provide a certificate to everyone.

So why could you get one for html-5.me ? Because I forgot to add it to the list of domains for subdomains. But that’s fixed now.

[anon3276028]

Of course, but that is not the point, I am talking about the ssl not trusted problem. When I installed LetsEncrypt ssl (of course I used this because admint forgot to do something, but I am not promoting) ssl not trusted problem is not seen, because browsers trust LetsEncrypt more than GoGetSSL or ZeroSSL. Thats what I am talking about.
@Admin @KangJL @belenn

[wackyblackie]

@anon3276028

browsers trust LetsEncrypt more than GoGetSSL or ZeroSSL.

That’s not a thing. Browsers (and/or operating systems) either trust the certificate or they don’t. There’s no “how much do I trust the certificate”. That said, there are certain caveats, like if your certificate is signed by a trusted root, which all Let’s Encrypt, GoGetSSL, and ZeroSSL certificates are. If your browser and/or operating system doesn’t like the certificate, its root store needs an update. Both ISRG Root X1 and X2 (with IdenTrust) and UserTrust should be in the trusted root certificates store, and thus should validate all certificates. This is mostly a problem with older devices, and applications that require their own root store.

Also, please stop mentioning people for no reason. Admin has pings turned off, and I’m sure that if KangJL doesn’t that it is very annoying, so please stop. And on top of that, posting replies that don’t improve the discussion or help solve a problem, are generally not needed (these are more reserved for the 10k topic, but that too has its limits).

[Admin]

@anon3276028

But installing LetsEncrypt have no problems like this. I think this is not a problem of free plan, it’s a problem of ssl providers.

The reason you didn’t encounter this “problem” is that it’s not really a “problem” for most people unless you look for it. But if you do look, you’ll see it also happens for Let’s Encrypt certificates:

That’s because, like the article linked by @wackyblackie says, this is a problem of CA chain support on free hosting, not a problem with the SSL certificate.

@wackyblackie

That’s not a thing. Browsers (and/or operating systems) either trust the certificate or they don’t. There’s no “how much do I trust the certificate”. That said, there are certain caveats, like if your certificate is signed by a trusted root, which all Let’s Encrypt, GoGetSSL, and ZeroSSL certificates are. If your browser and/or operating system doesn’t like the certificate, its root store needs an update. Both ISRG Root X1 and X2 (with IdenTrust) and UserTrust should be in the trusted root certificates store, and thus should validate all certificates. This is mostly a problem with older devices, and applications that require their own root store.

Actually, there is a grain of truth to it.

I’ve seen some cases where a device would not trust a Let’s Encrypt certificate initially, but it would after visiting a site with a Let’s Encrypt certificate with full CA chain. Most likely it had something to do with the intermediary cert having to be cached in the browser’s certificate store.

Let’s Encrypt is the most popular CA in the world, so the chance that a browser has encountered a Let’s Encrypt certificate before is much larger than a ZeroSSL or GoGetSSL certificate.

So the chance of this issue happening is larger with ZeroSSL or GoGetSSL.

But this particular error is not solved by switching to Let’s Encrypt, or any other SSL vendor for that matter.