letsencrypt - certbot - ubuntu: ERROR: Unable to find corresponding HTTP vhost; Unable to create one as intended addresses conflict
Hi,
I'm trying to use certbot from letsencrypt to set up my first SSL certificate. I'm running ubuntu 16 with apache.
I get this error message and I have no idea how to get to the bottom of this, if anyone can give me some guidance please. It's as if something is wrong with my apache? See the lines below that start with "unable to":
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/hollowplanets.com/fullchain.pem
Key is saved at: /etc/letsencrypt/live/hollowplanets.com/privkey.pem
This certificate expires on 2023-03-12.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.
Deploying certificate
Successfully deployed certificate for hollowplanets.com to /etc/apache2/sites-enabled/hollowplanets-le-ssl.conf
Successfully deployed certificate for www.hollowplanets.com to /etc/apache2/sites-enabled/hollowplanets-le-ssl.conf
Failed redirect for hollowplanets.com
Unable to set the redirect enhancement for hollowplanets.com.
NEXT STEPS:
- The certificate was saved, but could not be installed (installer: apache). After fixing the error shown below, try installing it again by running:
certbot install --cert-name hollowplanets.com
Unable to find corresponding HTTP vhost; Unable to create one as intended addresses conflict; Current configuration does not support automated redirection
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
2 Replies
✓ Best Answer
Do you have a VirtualHost definition (aka a vhost) for hollowplanets.com?
You might want to have a look at this:
https://www.linode.com/community/questions/23559/dont-delete-a-certificate-for-a-domain-via-certbot
— sw
Hi Stevewi,
Thank you very much for your answer. That link of yours is great because it also provides answers to other things I needed. e.g. Using one certificate for multiple domains.
The real thing that I was falling down on was that I did not have a VirtualHost definition for port 443. I had one for port 80. So once I added a definition for port 443 all was well.
Thanks again.