Hello I have a peculiar problem: On my server (Ubuntu 14.04 LTS) I have several virtual domains with a certificate from Let’s Encrypt. I have installed the certbot cronjob for automatic renewal. All was working since yet I think. In the weekly emails from cron I never found an error. When I got …

I had the same issue (Ubuntu 14.04). I had 3 different certificates/domains with very similar setups, and one was failing with "Failed authorization procedure" after following the instructions linked from the TLS-SNI-01 email: [image] How to stop using TLS-SNI-01 with Certbot Client…

[image] franc: ServerName voll-qualifizierter-Domainname[:port] It is allowed but not the recommended/normal. It can lead to a false sense of configuration. How does apache handle: <VirtualHost FQDN1:PORT1> ServerName FQDN2:PORT2 ServerAlias FQDN3:PORT3 How should that be handle…

[image] joohoi: To help Certbot development: if in any way possible, could you re-run Certbot with --debug-challenges - command line parameter? ... This gives me the same, if I select 1 in: 1: Apache Web Server plugin - Beta (apache) 2: Spin up a temporary webserver (standalone) 3: Place fil…

[image] franc: ServerName voll-qualifizierter-Domainname[:port] It may be defined / possible. But it's a source of potential problems. In the last months, I've never seen such a configuration in this forum. So it makes things easier if you remove that.

[image] franc: If I select webroot there is no error, this works. I guess, the 1. is the default. The "default" is found in the last renewal conf: [image] franc: /etc/letsencrypt/renewal/7fw.de.conf [image] franc: Is there something wrong with my Apache Web Server plugin? This …

[image] rg305: ... This seems not up-to-date: ... But how can I update that (Apache Web Server plugin - Beta)? And still, this canont be the error cause, the other domains are working. I took out the ports of the conf file for ServerName and ServerAlias but no change after that in the err…

[image] franc: But how can I update that (Apache Web Server plugin - Beta)? I would follow instructions that match the O/S and web server from here: https://certbot.eff.org/all-instructions/

[image] rg305: I would follow instructions that match the O/S and web server from here: https://certbot.eff.org/all-instructions/ That is exactly how I installed it in the first place, about half year ago.

What irritates me is, that in: /etc/letsencrypt/renewal/7fw.de.conf (and all the other working domains) the certbot version (?) is mentioned: version = 0.26.1 But when I command, I get: #certbot --version certbot 0.28.0

The renewal file just contains the last version of Certbot used to renew the certificate. If it hasn’t been renewed recently, it might not be the current version of Certbot you have now. It doesn’t necessarily indicate a problem.

[image] franc: [image] jawinn: I just tried your workaround using the --webroot version, and it worked: certbot certonly --webroot -w /var/www/foobar/public_html -d domain.com -d www.domain.com I tried a sudo certbot renew --dry-run again after this, and the error no longer occurs. I tr…

The client lacks sufficient authorization

Help

Topic		Replies	Views
Failed authorization procedure. Multiple virtualhosts apache Help	74	6302	August 21, 2018
Problem updating ACME TLS-SNI-01 to alternative validation method Help	241	10113	February 12, 2019
How To Force Certbot To Use Domain Name, Not Nameserver? Server	13	3297	October 2, 2018
Certbot failed to authenticate some domains Help	15	445	April 30, 2024
Invalid response creating certificate Help	36	1855	August 27, 2021

The client lacks sufficient authorization

Related topics