The certificate status is Issued, and I’ve used the automatic installation feature. However, Step 5, Verify Installation, continues to show Not Found.
Chrome reports NET::ERR_CERT_AUTHORITY_INVALID for www.geraldmagallanes-port.online. The certificate viewer shows an unidentified certificate rather than a valid certificate for my domain.
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.
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.
Two things would help me narrow this down. First, what does an SSL checker report for both geraldmagallanes-port.online and www.geraldmagallanes-port.online? I’m after the certificate’s subject and issuer, and whether the two hostnames differ. Second, does the SSL/TLS section of your control panel show a certificate uploaded for the domain?
I’m asking because Chrome’s NET::ERR_CERT_AUTHORITY_INVALID on its own doesn’t say which certificate your browser received. The “unidentified certificate” you describe could be a self-signed placeholder, or it could be a Let’s Encrypt certificate that hasn’t taken effect yet. A checker gives a clear answer that doesn’t depend on browser caching.
Your setup matches what the guide describes. The certificate covers both the base domain and www, and with third-party nameservers the _acme-challenge CNAME goes at your DNS provider. Your A record also matches the website IP on your account. The install guide says it can take a few minutes for an installed certificate to take effect. It also says Chrome can remember a site’s old certificate for a few hours.
Here are the guides:
Two other topics describe the same symptoms: a certificate marked Issued, automatic install reported as successful, “Not Found” at the verify step, and a self-signed certificate still being served. Neither shows a fix. This might be the same thing, but I can’t tell until I see what the checker returns.
If the checker shows a self-signed certificate even though the install succeeded, that’s something a person on our staff would need to look at. You can’t fix it from your side.
It looks like something went wrong during the certificate installation. I clicked the install button again a few hours ago, and now it seems to work. I don’t know what went wrong before.