Http-01 Challenge failed for domain

My domain is:

I ran this command: /usr/local/bin/certbot-auto --apache

It produced this output:

http-01 challenge for
Waiting for verification...
Challenge failed for domain
http-01 challenge for
Cleaning up challenges
Some challenges have failed.

 - The following errors were reported by the server:

   Type:   unauthorized
   Detail: Invalid response from
   2.0//EN\">\n<html><head>\n<title>404 Not
   Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p"

My web server is (include version):
Apache/2.2.22 (Ubuntu)

The operating system my web server runs on is (include version):
Ubuntu 12.10 (GNU/Linux 3.5.0-17-generic x86_64)

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

I wondered if my version of apache is too old to see the config changes made during the process of challenging the domain?

1 Like

WTF? Are you really using an 8 year old Ubuntu OS?

first of all, why are you validating the same domain twice?

you may want to use --webroot, but you need to read how it works. certbot -a webroot -w {fill this up} [-i apache]…

1 Like

Hi @Mehuge

if --apache doesn’t work, it may be

  • your apache is too old
  • your config is buggy (more then one combination port + domain)

What says

apachectl -S
1 Like
VirtualHost configuration:
wildcard NameVirtualHosts and _default_ servers:
*:80                   is a NameVirtualHost
         default server (/etc/apache2/sites-enabled/000-default:1)
         port 80 namevhost (/etc/apache2/sites-enabled/000-default:1)
         port 80 namevhost (/etc/apache2/sites-enabled/bb:2)
         port 80 namevhost (/etc/apache2/sites-enabled/cl:1)
         port 80 namevhost (/etc/apache2/sites-enabled/cu:1)
Syntax OK
1 Like


looks ok. May be Certbot has a problem because it’s the default server.

Try to add a new vHost, define that as default host with a dummy name (localhos etc.).

If that doesn’t work, switch to webroot. That should always work.


Note that this operating system has been out of support (and not receiving security updates) for about three years:

1 Like

That did not work. Will switch to webroot. Thanks

1 Like


your server is serving http on port 443:

check the virtualhosts again, and make sure to have an SSLEngine on directive for port 443

1 Like

Is there any way to get certbot to create the apache configs?

I ran certbot-auto certonly --webroot -w /var/www -d but I didn’t end up with any apache config for that domain.

1 Like

yes. certbot install --apache [-d domain.tld]


Thanks all. Sorted now.
I hand crafted the apache config in the end, it was fairly obvious given an example and the certificate file names.

1 Like

certbot didn’t install the cert because you explicitly asked it not to, by using certonly: had you not, certbot would have installed your cert.

you may want to look at this website:

1 Like

especially because of this:

and, oh, upgrade your os :smiley:

1 Like

Nahh. It’s a noddy test / dev server used for mostly ad-hoc dev stuff non of which is critical or at risk. Hell the login form for one of the sites pre-fills the user name and password for you (demo/demo) :slight_smile:

I do plan to spin up a new server at some point, but its way down the priority list atm.

Thanks for all your help though.

well… your tls keys are on that server. they might be for non-important sites, but they are secrets to be guarded.

1 Like

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