Issues updating certbot

Help
1

Hi there,

I'm having issue renewing my certificate and I think it maybe due to the version of certbot I'm using which is 1.16.0, however, I am having a big problem removing it as it isn't showing up in apt.

I can see that in the newer versions it uses snap which I don't have installed on the server so I must have installed it a different way. If anyone can help me with how to uninstall the old version and install the snap version it would be appreciated.

I don't want to assume the issue I have with the renewing the certificate is anything until I have updated certbot first.

Thanks,

Ed

1 Like
2

That probably is not the best way forward. While updating Certbot and using the snap install method is good that will just introduce other possible problems.

V1.16 is not horribly old so it would be better to evaluate what is going wrong and go from there.

What is the result of this command?

sudo certbot renew --dry-run

Also, we need to know more answers from the form you should have been shown. Different systems require different advice.

====================================

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:

I ran this command:

It produced this output:

My web server is (include version):

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

My hosting provider, if applicable, is:

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

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

4 Likes
3

My domain is: app.veeambp.com

I ran this command: certbot renew

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/app.veeambp.com.conf

Renewing an existing certificate for app.veeambp.com

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: app.veeambp.com
Type: unauthorized
Detail: 2a02:4780:b:1321:0:2a26:c84a:8: Invalid response from http://app.veeambp.com/.well-known/acme-challenge/maXwJNqy6K0ZPvZo5T_8aW81-0HckgL1z-LD2N8ui50: 404

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Failed to renew certificate app.veeambp.com with error: Some challenges have failed.

All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/app.veeambp.com/fullchain.pem (failure)

1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): nginx 1.14.0

The operating system my web server runs on is (include version): Ubuntu 18.04.6 LTS

My hosting provider, if applicable, is: Hostlinger

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): I don't have direct access to this someone else does, I'd need to check if still relevant.

Thanks,

Ed

1 Like
4

Here is the output of that comman;

Processing /etc/letsencrypt/renewal/app.veeambp.com.conf

Simulating renewal of an existing certificate for app.veeambp.com

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: app.veeambp.com
Type: unauthorized
Detail: 2a02:4780:b:1321:0:2a26:c84a:8: Invalid response from http://app.veeambp.com/.well-known/acme-challenge/oBqJ9MfU5PRpOgXGtYZ_u53Rh5HYy6Vic_pgfSJv7IA: 404

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Failed to renew certificate app.veeambp.com with error: Some challenges have failed.

All simulated renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/app.veeambp.com/fullchain.pem (failure)

1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

Other questions:

My domain is: app.veeambp.com

I ran this command: certbot renew

It produced this output: see above

My web server is (include version): Nginx 1.14.0

The operating system my web server runs on is (include version): Ubuntu 18.04.6 LTS

My hosting provider, if applicable, is: Hostlinger

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): I don't have access to this, I can confirm if needed.

Ed

5

On that IPv6 address, there's a LightSpeed server from the Hostinger platform reporting (with a "You Are All Set to Go!" default page), whereas on IPv4 your nginx is responding (with a "Welcome to nginx!" default page).

This discrepancy is usually caused by one of the two being incorrect, most likely your IPv6 address.

1 Like
6

Oh, yeah, Hostinger and wrong IPv6. We see that so often I have my own template for it. Osiris pointed you in the right direction. Maybe the extra bits below are further help.

Once you get your Certbot v1.16 working installing snap on Ubuntu should be easy. See: Certbot Instructions | Certbot Just follow the instructions carefully and test when you are done with sudo certbot renew --dry-run

You have both an IPv4 A record and an IPv6 AAAA record in your DNS

But, the IPv6 address points to a Hostinger service not your server. Hostinger creates this AAAA record automatically for new setups.

You need to update the AAAA address or remove it if you do not support IPv6.

Any client trying to use IPv6 will connect to that Hostinger service instead of your server.
Let's Encrypt favors IPv6 when an AAAA record is present.

See Hostinger article here: How to manage AAAA records | Hostinger Help Center

And use this site to test connections
https://letsdebug.net

4 Likes
7

Thanks for the advice, I'm looking at making these changes and will let you know if they work!

Ed

3 Likes
8

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