Related

How to fix permission error for /tmp/mongodb-27107.sock for Docker container running in AWS Question Question
Configuring virtual dev server - Apache question Question Question

Question

Certbot verification fails

Posted February 16, 2018 31.6k views
CentOSApacheLAMP StackLet's Encrypt

Certbot returns the error:

Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.

This is after a fresh install. I’m keeping it simple and not using any virtual hosts, etc. Just a few pages in the /var/www/html directory. httpd is enabled and I can access the website in my browser.

What am I doing wrong?

Add a comment
johns2ses
By:
johns2ses

Related

How to fix permission error for /tmp/mongodb-27107.sock for Docker container running in AWS Question Question
Configuring virtual dev server - Apache question Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
3 answers
kamaln7 February 21, 2018

As far as I know, Certbot supports virtual hosts only, so it won’t be able to proceed if you don’t have any configured. Try adding a basic virtual host like so and see if that helps:

<VirtualHost *:80>
    ServerAdmin admin@example.com
    ServerName example.com
    ServerAlias www.example.com
    DocumentRoot /var/www/html
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
Reply Report
wmcorless October 10, 2018

Also don’t forget to a2ensite 000-default

Reply Report
deatrich February 23, 2021

In case anyone else runs into this: I’ve run into this problem before (and again today); apache is endlessly configurable, and the certbot apache module is not able to cope with every configuration. I have the document root for various virtual hosts in different directories. Even though apache is quite happy with this, the certbot module is not always happy. I solved my problem using the –apache-vhost-root option:
# certbot –apache certonly –apache-vhost-root /var/www/html/www
and it solved my problem. For help see:
# certbot –help apache

Reply Report

Related

Looking for something else?

Ask a new question Search for more help