The client lacks sufficient authorization


I’m aware that this appeared many times, but no solution seems to work for me. I’m using the standalone plugin, no nginx or apache. the renewal worked for previous versions, now suddenly it doesn’t. It’s on an alibaba server,I think there are some problems with its configuration, because on other aws servers it just works.

My domain is:

I ran this command: sudo certbot renew

It produced this output:

Processing /etc/letsencrypt/renewal/

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for
Waiting for verification…

Exception happened during processing of request from (’::ffff:’, 46004, 0, 0)
Traceback (most recent call last):
File “/usr/lib/python3.5/”, line 313, in _handle_request_noblock
self.process_request(request, client_address)
File “/usr/lib/python3.5/”, line 341, in process_request
self.finish_request(request, client_address)
File “/usr/lib/python3.5/”, line 354, in finish_request
self.RequestHandlerClass(request, client_address, self)
File “/usr/lib/python3/dist-packages/acme/”, line 206, in init
BaseHTTPServer.BaseHTTPRequestHandler.init(self, *args, **kwargs)
File “/usr/lib/python3.5/”, line 681, in init
File “/usr/lib/python3/dist-packages/acme/”, line 215, in handle
File “/usr/lib/python3.5/http/”, line 422, in handle
File “/usr/lib/python3.5/http/”, line 410, in handle_one_request
File “/usr/lib/python3/dist-packages/acme/”, line 221, in do_GET
File “/usr/lib/python3/dist-packages/acme/”, line 246, in handle_simple_http_resource
File “/usr/lib/python3.5/http/”, line 524, in end_headers
File “/usr/lib/python3.5/http/”, line 528, in flush_headers
File “/usr/lib/python3.5/”, line 593, in write
return self._sock.send(b)
ConnectionResetError: [Errno 104] Connection reset by peer

Cleaning up challenges
Attempting to renew cert ( from /etc/letsencrypt/renewal/ produced an unexpected error: Failed authorization procedure. (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from []: “\n\n<meta http-equiv=“Content-Type” content=“textml;charset=UTF-8” />\n body{background-color:#FFFFFF}”. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/ (failure)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/ (failure)

1 renew failure(s), 0 parse failure(s)


  • The following errors were reported by the server:

    Type: unauthorized
    Detail: Invalid response from
    []: "\n\n<meta
    http-equiv=“Content-Type” content=“textml;charset=UTF-8” />\n


    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.

My web server is (include version): none? did not need until now

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

My hosting provider, if applicable, is: godaddy

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): 0.31.0


Hi @MeerKatDev

there are two problems ( ) : Your ipv6

Host T IP-Address is auth. ∑ Queries ∑ Timeout A yes 1 0
AAAA fe80::216:3eff:fe11:8cb1 yes Name Error yes 1 0

is a link local address, not a public, worldwide unique ip address. Letsencrypt may ignore that error.


Domainname Http-Status redirect Sec. G -2 1.677 V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 200 3.530 B -2 1.640 V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it
Visible Content:

Your port 80 is blocked. Port 80 must be open if you want to use http-01 validation.

Perhaps you have used tls-sni-01 validation (port 443), that’s deprecated, not longer supported.


Hi, thank you very much. And is it possible to verify through some other port other than 80?


You can use tls-alpn-01 - validation. But Certbot doesn’t support that.

Or dns-01 - validation, then a dns entry is required.



A closed port 80 isn’t a “more secure system”. You can add redirects http -> https.

1 Like

Unluckily it’s not me deciding for that port. It’s blocked due to external reasons (Chinese law).
What do I run for renewal with dns? I searched by and large but all I’ve found is about only creation with dns-01.
And how do I get the token to put in the TXT record? I understand that it should be called (?), right?


That’s the same.


certbot -d --preferred-challenges dns --manual

then Certbot shows the txt entry you have to use.

closed #7

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