Could not reverse map the HTTPS VirtualHost to the original

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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: rsdrive.frame-shutter.com

I ran this command: sudo certbot --apache

It produced this output:

Successfully received certificate.

Certificate is saved at: /etc/letsencrypt/live/rsdrive.frame-shutter.com/fullchain.pem

Key is saved at: /etc/letsencrypt/live/rsdrive.frame-shutter.com/privkey.pem

This certificate expires on 2025-04-26.

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

Could not install certificate

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 rsdrive.frame-shutter.com

Could not reverse map the HTTPS VirtualHost to the original

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.

My web server is (include version): Apache

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

My hosting provider, if applicable, is: Home Server

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): certbot 3.1.0

Apache is listening unencrypted on port 443. http://rsdrive.frame-shutter.com:443/ (this usually isn't what you want)

You might have better luck configuring Apache manually, if you know how your VirtualHosts are configured:

3 Likes