Net::err_cert_common_name_invalid

Help
1

Hello,

My domain is: www.heyoapps.com

I ran this command: https://www.heyoapps.com

It produced this output:

NET::ERR_CERT_COMMON_NAME_INVALID

...

It's on a shared host with letsencrypt SSL install. We are getting "NET::ERR_CERT_COMMON_NAME_INVALID" error on Chrome while browsing the site on https://www.heyoapps.com and it resolves to another website which we really don't know and own.

The hosting provider tells us that it's a widespread issue on LetsEncrypt and they cannot solve it until you solve the issue.

What shall I do? How do you help us? It's really annoying that users are seeing an insecure and unrelated website on our domain.

Regards,

2

Hi @theoryginal and welcome to the LE community forum :slight_smile:

Certificates were issued to your names (heyoapps.com & www.heyoapps.com) two weeks ago.
The problem that the shared hosting system isn't serving those certs for your name is not possibly due to anything LetsEncrypt (LE) has done. All they did was issue your certs.

Call your ISP and ask to speak with a real IT person.
Show them this link:
SSL Server Test: www.heyoapps.com (Powered by Qualys SSL Labs)

1 Like
3

Hi,
Thank you for your response. I forwarded your message to our hosting provider with the SSL Test link.

I wouldn't be bothering you here if they hadn't told me I should wait for LetsEncrypt (LE) to solve the issue, so now we are more clear about the issue.

Let me see...

Thank you

1 Like
4

No problem, you are very welcomed here.
Cheers from Miami :beers:

#FreeCUBA :cuba:

1 Like
5

@theoryginal Currently, your site uses a Let's Encrypt certificate issued today at 12:17 UTC which, among others, includes your site. So it seems your hosting provider fixed the issue and I assume your issue has been resolved. Can you confirm that?

2 Likes
6

Yes I contacted with the hosting provider they configured the certificate again in a proper way.
Now SSL looks OK, but the site is redirecting to root domain of the shared hosting without a reason which is the issue hosting provider must solve.

So yes in certificate-wise my issue is resolved!

Thank you all of you and your prompt replies,

They were really insightful for me to understand and solve the issue.

Sincerely,

2 Likes
7

I see that; now:

http://heyoapps.com/     > http://www.heyoapps.com/   [GOOD]
http://www.heyoapps.com/ > https://www.heyoapps.com/  [GOOD]
https://heyoapps.com/    > http://www.heyoapps.com/ > https://www.heyoapps.com/ [WEIRD]
https://www.heyoapps.com/  [GOOD]
1 Like
8

Yes now we also solved that alias redirect issue from hosting provider side :slight_smile:
All looking good, up and kicking!

1 Like
9

Glad to hear that :slight_smile:
Cheers from Miami :beers:

#FreeCUBA :cuba:

1 Like
10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.