Installing Certbot Problems

My domain is:

I ran this command: N/A

It produced this output: N/A

My web server is (include version): I don’t know

The operating system my web server runs on is (include version): I don’t know

My hosting provider, if applicable, is: namecheap

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

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): N/A

Hi everyone, thanks in advance for any help.
I woke up this morning to check my email and I got a notification in the mail app saying my certificate expired. I remember this happening earlier, and I managed to fix it. I’m decently okay with tech but all the background certificates and DNS and SSL and SSH, not so much ! I found this CertBot option, and I’ve used terminal before so I wasn’t super intimidated, but I can’t even get past the question of what I’m using hahah. I know namecheap uses Apache, but for what my site in running on, I’m technically using namecheap, no ? I use OSx, which is also an option. But when I put Apache on web hosting service, there are no instructions.

Anyway, I picked Apache on OSx, since it has instructions. But the first instruction, SSH into the server running your HTTP website as a user with sudo privileges, I don’t know how to do that ? I did google it, but, no luck ?

I’m very sorry I am so embarrassed and feel like such an idiot but I’ve been sitting here for hours and I really need help.

Hi @beellllaa

I don't understand your informations.

You have a lot of older certificates -

Startet 2018-02-26.

The last three:

CRT-Id Issuer not before not after Domain names LE-Duplicate next LE
leaf cert CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-07-31 03:08:37 2019-10-29 04:08:37,,,,,,
7 entries
leaf cert CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-05-31 03:08:54 2019-08-29 03:08:54,,,,,,
7 entries
leaf cert CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US 2019-03-31 03:07:55 2019-06-29 03:07:55,,,,,,
7 entries

The newest is active, created via cPanel. Your last not-cPanel-certificate is from 2018, that doesn't send a mail.

And your current certificate doesn't send a mail, it's too new.

cPanel should update your certificate, check it again 2019-10-20.

Hi @JuergenAuer !

Thank you for your reply !
Honestly, I don’t really know…

This is the message I have from Mail. I know I saw this before in the beginning of the summer, and I managed to fix it and make the message go away by renewing my certificate, but I don’t remember how I did this.

Does the latest lead cert mean that my certificate did auto-renew and Mail doesn’t know it ? Do I have to fix it ?

That’s the mail subdomain.

Checking that subdomain there is the same certificate -
expires in 41 days,,,,,, - 7 entries

The mail subdomain is included.

So I don’t understand your screenshot.

Oh, wait: Is your computer time correct? “Expires - Tuesday, 29 October 2019” - then “has expired”.

–> The time of your computer may be wrong.

I live in France, so my time is correct for my timezone. That’s never been a problem for me though. I use a VPN ?

Are you sure that message isn’t spam? Why is DST Root and the Letsencrypt certificate marked with a red x?

I think the x is Mac’s error symbol for this stuff. It’s saying my domain has an error, which is found in Let’s Encrypt Authority X3, which is in the DST Root CA X3 folder. Then it says the error is that my domain certificate has expired

I don’t see how it could be spam with it’s not an email, it’s a notification pop up in the Mail app. It’s disallowing me to click out and use the mail app.

I see the certificate on the mail server as totally valid and unexpired, so I think the problem is on your computer somehow, even though the desktop interface seems to show that the clock is set properly.

@schoen @JuergenAuer

I’ve since quit and reopened Mail with the same problem, but then reset my computer and I’m not getting the error anymore. I’m hoping it’s fixed itself hahaha.

But should I still install certbot ?

Hi @beellllaa,

In this case, Certbot is an alternative to cPanel for this purpose, and it doesn’t really make sense to use Certbot if you’re using cPanel. I don’t think that your problem is likely to be related to anything that could be fixed by switching to Certbot.

Ah okay, very fun hahah. Eh, question - sorry. I just use the interface from namecheap, not the cPanel website. Is that the same thing, since namecheap says they use cpanel ?

Yes, it seems clear that you’re using an instance of cPanel provided by NameCheap.

Thank you @schoen so much for your patience :slight_smile: We’ll see next month what happens !

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