Fixing “Could not Reverse Map the HTTPS VirtualHost to the original” error
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi there,
This usually happens when Apache can’t properly map the HTTPS request back to the correct VirtualHost.
You should double-check that your ServerName and ServerAlias are correctly set in your SSL VirtualHost block.
Also, make sure you don’t have overlapping or missing VirtualHost definitions.
Then, restart Apache after any changes with sudo systemctl restart apache2 and it should clear up.
Let me know how it goes.
- Bobby
Heya, @301276acdc124dd982fe86364ba8c4
The error “Could not Reverse Map the HTTPS VirtualHost to the original” happens because Apache can’t properly match your server’s hostname to a ServerName or ServerAlias.
To fix it, inside your VirtualHost for port 443 (<VirtualHost *:443> or <VirtualHost _default_:443>), add:
ServerName yourdomain.com
Then restart Apache:
sudo systemctl restart apache2
Regards
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.