Failed authorisation procedure

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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain

I ran this command: sudo ./certbot-auto  certonly --standalone

It produced this output:
I have created a subdomain, and want to create a “proper” certificate
because I am tired of getting “untrusted” error messages.
Letsencrypt gives me an error message:
Failed authorization procedure. (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from

" To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address."
The domain name I entered was

The A record contains handel

My web server is (include version): Chrome Version 69.0.3497.100 (Official Build) (64-bit)

The operating system my web server runs on is (include version):Mageia 6 x86.64

My hosting provider, if applicable, is: IONOS

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): LE_AUTO_VERSION=“0.30.2”

Hi @ggemmill

your main configuration looks ok ( - Make your website better - DNS, redirects, mixed content, certificates ):

Domainname Http-Status redirect Sec. G 200 0.100 H 200 0.093 H 200 1.764 N
Certificate error: RemoteCertificateNameMismatch 200 1.527 N
Certificate error: RemoteCertificateNameMismatch 404 0.103 A
Not Found 404 0.260 A
Not Found

If you use http-01 validation, Certbot creates a file under /.well-known/acme-challenge, Letsencrypt checks this file. Port 80 is open, your webserver sends the expected http status 404, if the file is unknown.

So check your config to find your DocumentRoot (in your port 80 - vHost). Then use it:

sudo certbot run -a webroot -i apache -w YourDocumentRoot -d

It seems certbot is unable to identify which vhost (or root directory) is managing "".
The logs might give more precise detail on this.
Or you can review your vhost configs.

This doesn't seem correct:

That's a web browser (not server)

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