# Apache2 server Certbot Unable to find corresponding HTTP vhost **URL:** \ **Category:** Help\ **Created:** [June 27, 2023, 4:03pm UTC](https://community.letsencrypt.org/t/apache2-server-certbot-unable-to-find-corresponding-http-vhost/200854 "2023-06-27T16:03:37Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![cocolinofan](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@cocolinofan](https://community.letsencrypt.org/u/cocolinofan)\ **Post date:** [June 27, 2023, 4:03pm UTC](https://community.letsencrypt.org/t/apache2-server-certbot-unable-to-find-corresponding-http-vhost/200854/1 "2023-06-27T16:03:37Z")
My domain is: cocolino.top I ran this command: certbot --apache It produced this output: certbot --apache Saving debug log to /var/log/letsencrypt/letsencrypt.log Unable to read ssl\_module file; not disabling session tickets. Which names would you like to activate HTTPS for? We recommend selecting either all domains, or all domains in a VirtualHost/server block. * * * 1: cocolino.top * * * Select the appropriate numbers separated by commas and/or spaces, or leave input blank to select all options shown (Enter 'c' to cancel): 1 Certificate not yet due for renewal You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry. (ref: /etc/letsencrypt/renewal/cocolino.top.conf) What would you like to do? * * * 1: Attempt to reinstall this existing certificate 2: Renew & replace the certificate (may be subject to CA rate limits) * * * Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1 Deploying certificate Successfully deployed certificate for cocolino.top to /etc/apache2/vhosts.d/00\_default\_vhost-le-ssl.conf Failed redirect for cocolino.top Unable to set the redirect enhancement for cocolino.top. 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 cocolino.top 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](https://community.letsencrypt.org). See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. My web server is (include version): Server version: Apache/2.4.57 (Unix) The operating system my web server runs on is (include version): OS: Gentoo Linux x86\_64 6.3.9-gentoo-dist ## My hosting provider, if applicable, is: I can login to a root shell on my machine (yes or no, or I don't know): yep I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No, I am editing file in apache config. The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): certbot 2.6.0 I can provide the contents of the apache2 configuration files if something needs to be changed there. /var/log/letsencrypt/letsencrypt.log can be found here: [https://bpa.st/6W232](https://bpa.st/6W232) ---
**Author:** ![cocolinofan](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@cocolinofan](https://community.letsencrypt.org/u/cocolinofan)\ **Post date:** [June 27, 2023, 5:41pm UTC](https://community.letsencrypt.org/t/apache2-server-certbot-unable-to-find-corresponding-http-vhost/200854/2 "2023-06-27T17:41:18Z")
[FIXED] 1. On Gentoo "mod\_ssl.so" is not located in "/etc/apache2/modules" but in "/usr/lib64/apache2/modules/mod\_ssl.so". There isn't even a "/etc/apache2/modules" folder on Gentoo it is called "modules.d"! How I fix: -mkdir /etc/apache2/modules -cp /usr/lib64/apache2/modules/mod\_ssl.so /etc/apache2/modules/mod\_ssl.so 2. I am embarrassed to say but I forgot to forward port 443 on my router, after that was done, no more errors. 😳 ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [June 27, 2023, 6:04pm UTC](https://community.letsencrypt.org/t/apache2-server-certbot-unable-to-find-corresponding-http-vhost/200854/3 "2023-06-27T18:04:51Z")
Note that the warning about "Unable to read ssl\_module file; not disabling session tickets." doesn't have anything to do with the "Unable to find corresponding HTTP vhost; Unable to create one as intended addresses conflict; Current configuration does not support automated redirection" warnings. It's kinda weird tho that Certbot did deploy the certificate correctly (so with that step there weren't any issues with address conflicts), but afterwards couldn't set up the redirect? Your Apache configuration might be a little bit non-standard I believe. ---
**Author:** ![cocolinofan](https://avatars.discourse-cdn.com/v4/letter/c/f0a364/32.png) [@cocolinofan](https://community.letsencrypt.org/u/cocolinofan)\ **Post date:** [June 27, 2023, 9:24pm UTC](https://community.letsencrypt.org/t/apache2-server-certbot-unable-to-find-corresponding-http-vhost/200854/4 "2023-06-27T21:24:05Z")
I do my best to keep it standard, well as standard as you can on Gentoo. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [June 28, 2023, 5:23am UTC](https://community.letsencrypt.org/t/apache2-server-certbot-unable-to-find-corresponding-http-vhost/200854/5 "2023-06-28T05:23:57Z")
True, but I run Gentoo too and I haven't seen this error before to be honest 🙂 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [July 28, 2023, 5:24am UTC](https://community.letsencrypt.org/t/apache2-server-certbot-unable-to-find-corresponding-http-vhost/200854/6 "2023-07-28T05:24:34Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.