Using HTTP-01 Challange on SubDomain


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

I ran this command: /usr/etc/certbot-auto renew --dry-run

It produced this output: 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\n403 Forbidden\n\n


\n<p”. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/ (failure)
/etc/letsencrypt/live/ (failure)

My web server is (include version): Apache

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

My hosting provider, if applicable, is:

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

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.30.2


The Error mentioned is only occuring on subdomain vhost. With direct Domain vhost it is working. The Vhost config of this hosts is copied and only path is changed. When i manually place a file in .well-known/acme-challenge this file is accessible given that the file Rights are set correctly read Access for all.

Thanks in advance


Hi @sh10

curious: I don’t see a 403, instead a 404 ( ):

If you use only --dry-run, there may be an older configuration so you use the standalone-version.

But if you have created a test file and if you can see the test file in your browser, you should have your correct webroot. So use this:

certbot run -a webroot -w yourWebRoot -d --dry-run

Oh - what’s that? You have already a certificate created yesterday.
	29.04.2019 - 1 entry


Hello @JuergenAuer

Thank you. With your tip it was now possible for me to Change My update
Script to new Interface.

The Error 404 is clear as i have separater VHosts which are only active when update script is executed.

The certificate from 29.01 was also clear as i updated the certs again before i updated certbot to move to http-01.

closed #4

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