Certificate Name Does Not Match Input

I'm trying to create an SSL certificate and getting a certificate however it now says it doesn't match the input on the certificate. I successfully did this on another sub domain of mine so not sure what has happened.

My domain is: www.muckersiesmovements.com

I ran this command: n/a - manually trying to create an SSL certificate

It produced this output: error on the website saying the URL doesn't match the input

My web server is (include version): not sure

The operating system my web server runs on is (include version): not sure

My hosting provider, if applicable, is: Tsohost

I can login to a root shell on my machine (yes or no, or I don't know): No

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Yes, cPanel 118.0.13

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): not sure

  • "Do you want a green or a red apple?"
  • -"Yes"
  • :thinking: :question: :roll_eyes:

Anyway:

How exactly? Please show screenshots if you can't explain in detail.

1 Like

I've updated the above now to reflect the version of cPanel.

I'm using this guide - CertSage ACME client (version 1.4.2) - easy webpage interface, optimized for cPanel, no commands to type, root not required. Although I used the 1.3.0 older version

EDIT - It appears to be working now. Very odd...!

2 Likes

It's a good idea to update CertSage to the most recent version. But it's helpful to know you are using CertSage.

There's no such error in CertSage. There are the following errors with "[mis]match" in them in v1.3.0:

  • csr format mismatch;
  • certificate format mismatch;
  • certificate key format mismatch.

but those don't really sound like what you were saying?

Weird indeed.

1 Like

You are correct, @Osiris. CertSage also reports back errors directly from Let's Encrypt, so maybe something from Boulder? I can't recall offhand any error messages from Boulder similar to what @muck9 has reported though. :thinking:

2 Likes

Or an error from cPanel at the installation step?

1 Like

That's possible too. CertSage uses uapi and not the url-api for cPanel, so not sure how.

I'm not sure if you were meaning manually from cPanel, which is another possibility.

2 Likes

I third this notion.

2 Likes

To be clearer, the error I noted above was from safari when I clicked on the padlock next to the URL in the URL box at the top. It didn’t give me this error through CertSage. Should’ve mentioned that initially!

2 Likes

That kinda sounds like the certificate doesn't cover the (sub)domain name in the URL, which usually indicates that either the "www" subdomain name or the apex domain name (no subdomain) wasn't included on the list to certify.


Update: Not www or apex. Perhaps another subdomain name missing?

https://decoder.link/sslchecker/muckersiesmovements.com/443

https://decoder.link/sslchecker/www.muckersiesmovements.com/443

4 Likes

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