The client lacks sufficient authorization :

Help
1

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. https://crt.sh/?q=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:
lallybroch.com.au

I ran this command:
sudo certbot
certonly
–rsa-key-size 4096
–dns-cloudflare
–webroot -w /var/www/lallybroch.com.au
–installer nginx
–dns-cloudflare-credentials /etc/letsencrypt/.secrets/certbot/cloudflare.ini
–dns-cloudflare-propagation-seconds 60
-d lallybroch.com.au
-d www.lallybroch.com.au
–post-hook “service nginx start”
–post-hook “service nginx stop”

It produced this output:
Performing the following challenges:
http-01 challenge for lallybroch.com.au
http-01 challenge for www.lallybroch.com.au
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. www.lallybroch.com.au (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.lallybroch.com.au/.well-known/acme-challenge/OL4GBp-ilnNznT_T3u2r8tLvCrAUkL5rtjzPCgS-Nqw [2606:4700:30::6812:2df0]: "\n\n<!–[if IE 7]> <html class="no-js ", lallybroch.com.au (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://lallybroch.com.au/.well-known/acme-challenge/AJb7ClfAYAztPsIwAzzYb8qzCuBQNxguzh4BTyvBc3I [2606:4700:30::6812:2cf0]: "\n\n<!–[if IE 7]> <html class="no-js "

My web server is (include version):

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

My hosting provider, if applicable, is:
Cloudflare

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):
certbot 0.28.0

2

your option looks strange. both webroot and dns parameters. what kind of challenge you want to? HTTP-01 or DNS?
and your post hook will leave nginx stop after this. is this indended?

1 Like
3

Hi @StuRams

you mix two authentication methods: dns-01 via cloudflare and webroot. So webroot is used and dns-01 is ignored.

And if you have certonly, then installer can't work.

A typical command may be:

sudo certbot certonly --rsa-key-size 4096 --dns-cloudflare --dns-cloudflare-credentials /etc/letsencrypt/.secrets/certbot/cloudflare.ini --dns-cloudflare-propagation-seconds 60 -d lallybroch.com.au -d www.lallybroch.com.au

Stopping / starting nginx isn't relevant if you use certonly.

Your domain is invisible - https://check-your-website.server-daten.de/?q=lallybroch.com.au - so webroot can't work.

1 Like
4

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