How to renew a 90 day cert before expiry date reached

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: footiefantasy.eu

I ran this command:

It produced this output:

My web server is (include version):raspberry pi 4

The operating system my web server runs on is (include version):linux apache 2

My hosting provider, if applicable, is: reg-123

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):no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):sudo certbot --manual --preferred-challenges dns certonly -d footiefantasy.eu

Good Morning,
I installed a letsencrypt cert (90 Day) to my server and its about to expire on 7th November. I installed it using the following command:
sudo certbot --manual --preferred-challenges dns certonly -d footiefantasy.eu

My question is do I need uninstall this cert or just install another cert using my original process. If there is a special process for re-initiating this cert could you point me to how to do this please.

Thank you for your time.
Kind regards Don....

1 Like

You're using the manual plugin, which isn't easily to automate. Usually one would simply run sudo certbot renew, but that doesn't work with the manual plugin if no hooks are used.

Why are you using the manual plugin? For which service is the certificate used? A webserver? If so, which one?</> Ah, Apache, was filled out in an incorrect question.

Why not use the apache plugin with sudo certbot --apache ? If that works, you can simply run sudo certbot renew, which is usually done using a regular cronjob or systemd timers.

Hi, I am using the manual method because my ISP blocks both ports 80 and 443 and this was the only way of installing the cert as advised by youself...
Kind regards Don...

there is dns-01 plugin for godaddy

4 Likes

Hi, My domain is not with godaddy but 123-reg. This godaddy api looks way above my pay grade. I just want to know do I renew using the manual method again or do I need to remove the old cert, or is there anything else I need to be aware of.??
Kind regards Don....

Your registrar and your DNS provider can be different companies. I don't know if that's the case here.

But you can always choose who your DNS provider is, without changing registrar. Common options include cloudflare, hurricane electric, etc...

4 Likes

Yes, without hooks a cert using the manual plugin can only be renewed by running the same command over and over again manually per renewal. I.e., every 60 days.

Using the GoDaddy plugin Certbot can be automated. But I'm not a fan of the (developer of the) plugin, as it has some "interesting" choices regarding the handeling of dependencies. (Incorrectly IMO..)

1 Like

Hi, thank for your reply. My cert is over 60 days old, does that make any difference to the manual renewal (I thought certs were good for 90 days).

Also, do you know what the certbot command is to activate the cert when it has been installed. Ive forgotten it and cant find it anyway on google ?

Kind regards Don...

1 Like

certbot install -i apache

Should be what you're looking for.

You can combine both:

certbot --authenticator manual --installer apache [etc etc]

3 Likes

The DNS is with GoDaddy:

footiefantasy.eu        nameserver = ns29.domaincontrol.com
footiefantasy.eu        nameserver = ns30.domaincontrol.com

[DomainControl is a domain GoDaddy uses for DNS]

4 Likes

Good morning, I manually re-installed the cert as if it was the first time I had installed it with this command:
sudo certbot --manual --preferred-challenges dns certonly -d footiefantasy.eu.
Then replaced the new cert number with the original cert number with my DNS provider. Rebooted the apache 2 server and it worked flawlessly. The cert is now renewed for another 3 months.
Thank you to eveyone who helped me resolve this problem.

1 Like

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