Cannot resolve incorrect common name domain in cert

Website, Application, Performance Security
1

What is the name of the domain?

worstnewz.com

What is the error message?

site shows as insecure (no SSL) because cert has a common name for another domain

What is the issue you’re encountering

site shows as insecure (no SSL) because cert has a common name for another domain

What steps have you taken to resolve the issue?

I’ve added and revoked worstnewz ssl certs using certbots to the point that now I’m blocked 24 hours for 5 attempts.

I am bringing back worstnewz.com after I took it down a couple years ago, if that’s at all relevant.

I’m attempting to let Cloudflare handle all SSL as letsencrypt / certbot has always caused me grief from day one, years ago.

Was the site working with SSL prior to adding it to Cloudflare?

Yes

What is the current SSL/TLS setting?

Full

What are the steps to reproduce the issue?

go to worstnewz.com in the browser. Click on left side of address bar and view cert details and find it has a common name for another domain I run on the same server.

2

to be clear, I have as of now revoked all certs and traces of letsencrypt and certbot on my server.

3

this appears to have resolved itself now. Maybe was an issue with making so many SSL changes so fast, maybe propagation was the thing.

1 Like
4

I see a database error now. That’s obviously on the origin side.

Good luck!

5

Thanks, yeah, I did not do enough reading up on the Cloudflare SSL certs before I dove in.

Now I have new questions:

  1. I tried creating an Cloudflare Origin CA cert. I got as far as creating one for one of my domains but nowhere do I see what filename to use.
  2. I need to go through this whole CSR step then?? I might as well go back to certbot if that’s the case.
6

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