# Bug: Could not reverse map the HTTPS VirtualHost to the original
**URL:** https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731
**Category:** Help
**Created:** [May 16, 2019, 12:49pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731 "2019-05-16T12:49:42Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 16, 2019, 12:49pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/1 "2019-05-16T12:49:43Z")
I deleted all virtual host files and created them clean again because I had a redirection loop. I enabled all conf files using a2ensite www.kekschen.eu.conf for all domains. However I ran into a bug. I attached all conf files and the log: [https://1drv.ms/u/s!ArWVG-HsH4lKkeBWd2Do5CeMOuc3Yw](https://1drv.ms/u/s!ArWVG-HsH4lKkeBWd2Do5CeMOuc3Yw)
My domain is: config.png.services, png.services, kekschen.eu, www.png.services, www.kekschen.eu
I ran this command:
certbot --apache -d png.services -d www.png.services -d kekschen.eu -d www.kekschen.eu -d config.png.services
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Cert 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/png.services.conf)
What would you like to do?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Attempt to reinstall this existing certificate
2: Renew & replace the cert (limit ~5 per 7 days)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1
Keeping the existing certificate
Could not reverse map the HTTPS VirtualHost to the original
IMPORTANT NOTES:
- Unable to install the certificate
- Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/png.services/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/png.services/privkey.pem
Your cert will expire on 2019-08-14. To obtain a new or tweaked
version of this certificate in the future, simply run certbot again
with the "certonly" option. To non-interactively renew *all* of
your certificates, run "certbot renew"
root@png:/etc/apache2/sites-available#
```
My web server is (include version): Apache2
The operating system my web server runs on is (include version): Ubuntu 18.10
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 0.31.0
---
### Author:  [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)
#### Post date: [May 16, 2019, 1:23pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/2 "2019-05-16T13:23:35Z")
Hi @Philipp97714
> [@Philipp97714](#):
>
> certbot --apache -d png.services -d www.png.services -d kekschen.eu -d www.kekschen.eu -d config.png.services
looks like you have changed your vHost configuration. So Certbot can't find one vHost with these domain names.
What says
```nohighlight
apachectl -S
```
If you have different vHosts (one per non-www and www-domain), create new different certificates.
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 16, 2019, 1:27pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/3 "2019-05-16T13:27:13Z")
I just deleted all conf files in sites-availble and all links in site-enabled. I thought certbot would create all virtualhosts for https again if I create those for port 80
```
root@png:/etc/apache2/sites-available# apachectl -S
VirtualHost configuration:
207.180.236.50:80 is a NameVirtualHost
default server config.PNG.Services (/etc/apache2/sites-enabled/config.png.services.conf:1)
port 80 namevhost config.PNG.Services (/etc/apache2/sites-enabled/config.png.services.conf:1)
alias config.PNG.Services
port 80 namevhost kekschen.eu (/etc/apache2/sites-enabled/kekschen.eu.conf:1)
alias kekschen.eu
port 80 namevhost PNG.Services (/etc/apache2/sites-enabled/png.services.conf:1)
alias PNG.Services
port 80 namevhost www.kekschen.eu (/etc/apache2/sites-enabled/www.kekschen.eu.conf:1)
alias www.kekschen.eu
port 80 namevhost www.PNG.Services (/etc/apache2/sites-enabled/www.png.services.conf:1)
alias www.PNG.Services
*:80 vmd33584.contaboserver.net (/etc/apache2/sites-enabled/default.conf:1)
*:443 vmd33584.contaboserver.net (/etc/apache2/sites-enabled/default.conf:32)
ServerRoot: "/etc/apache2"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/var/log/apache2/error.log"
Mutex watchdog-callback: using_defaults
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default
Mutex mpm-accept: using_defaults
PidFile: "/var/run/apache2/apache2.pid"
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
User: name="www-data" id=33
Group: name="www-data" id=33
```
---
### Author:  [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)
#### Post date: [May 16, 2019, 1:30pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/4 "2019-05-16T13:30:06Z")
> [@Philipp97714](#):
>
> port 80 namevhost www.kekschen.eu (/etc/apache2/sites-enabled/www.kekschen.eu.conf:1) alias www.kekschen.eu
Do you really have ServerName and ServerAlias with the same name?
Alias should be another name.
Typical:
```nohighlight
ServerName kekschen.eu
ServerAlias www.kekschen.eu
```
then a certificate with both domain names.
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 16, 2019, 1:42pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/5 "2019-05-16T13:42:20Z")
So I just need one virtualhost for [www.example.com](http://www.example.com) and [example.com](http://example.com)? If I browse to any domain, will I always be redirected to its www. subdomain?
---
### Author:  [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)
#### Post date: [May 16, 2019, 1:54pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/6 "2019-05-16T13:54:49Z")
> [@Philipp97714](#):
>
> So I just need one virtualhost for [www.example.com](http://www.example.com) and [example.com](http://example.com)?
Yes, that's the standard handling of a domain with non-www and www.
> [@Philipp97714](#):
>
> If I browse to any domain, will I always be redirected to its www. subdomain?
You have to create a correct redirect. But it's easier to do such things if you have only one main domain name per vHost.
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 16, 2019, 1:59pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/7 "2019-05-16T13:59:38Z")
Okay I delete all www.\*.conf files and change the remaining ones as you said, right? Do I have to change anything else because you said something of a correct redirect?
> [@JuergenAuer](#):
>
> You have to create a correct redirect.
> [@JuergenAuer](#):
>
> ServerName kekschen.eu ServerAlias www.kekschen.eu
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 16, 2019, 4:45pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/8 "2019-05-16T16:45:11Z")
I did what you said and removed all www.\*.conf files and added a "www." to ServerAlias. This didn't solve the issue.
> root@png:/etc/apache2/sites-available# certbot --apache -d png.services -d kekschen.eu -d config.png.services
> Saving debug log to /var/log/letsencrypt/letsencrypt.log
> Plugins selected: Authenticator apache, Installer apache
>
> * * *
>
> You have an existing certificate that contains a portion of the domains you
> requested (ref: /etc/letsencrypt/renewal/png.services-0001.conf)
>
> It contains these names: png.services
>
> You requested these names for the new certificate: png.services, kekschen.eu,
> config.png.services.
>
> Do you want to expand and replace this existing certificate with the new
> certificate?
>
> * * *
>
> (E)xpand/(C)ancel: E
> Renewing an existing certificate
> Could not reverse map the HTTPS VirtualHost to the original
>
> IMPORTANT NOTES:
>
> - Unable to install the certificate
> - Congratulations! Your certificate and chain have been saved at:
> /etc/letsencrypt/live/png.services-0001/fullchain.pem
> Your key file has been saved at:
> /etc/letsencrypt/live/png.services-0001/privkey.pem
> Your cert will expire on 2019-08-14. To obtain a new or tweaked
> version of this certificate in the future, simply run certbot again
> with the "certonly" option. To non-interactively renew _all_ of
> your certificates, run "certbot renew"
---
### Author:  [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)
#### Post date: [May 16, 2019, 4:47pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/9 "2019-05-16T16:47:56Z")
> [@Philipp97714](#):
>
> certbot --apache -d png.services -d kekschen.eu -d config.png.services
That's completely wrong.
One vHost with domain and www.domain. One certificate with
-d domain -d www.domain.
Not different vHosts mixed.
```nohighlight
certbot --apache -d kekschen.eu -d www.kekschen.eu
```
but only, if you have a vHost with
```nohighlight
ServerName kekschen.eu
ServerAlias www.kekschen.eu
```
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 16, 2019, 4:52pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/10 "2019-05-16T16:52:53Z")
My kekschen.eu.conf has the following content:
> ```
>
> ServerAdmin Philipp@PNG.Services
> ServerName kekschen.eu
> ServerAlias www.kekschen.eu
>
> DocumentRoot /var/www/kekschen/html
> ErrorLog ${APACHE_LOG_DIR}/error.log
> CustomLog ${APACHE_LOG_DIR}/access.log combined
>
>
>
> AllowOverride All
>
>
> ```
```
certbot --apache -d kekschen.eu -d www.kekschen.eu
```
produces the same error
---
### Author:  [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)
#### Post date: [May 16, 2019, 4:56pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/11 "2019-05-16T16:56:04Z")
What's that?
> [@Philipp97714](#):
>
> ```nohighlight
>
>
> ```
This isn't a place used with a domain name. Use
```nohighlight
```
so this VirtualHost uses all ip addresses.
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 16, 2019, 6:34pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/12 "2019-05-16T18:34:24Z")
I changed it but it is still not working. I guess it is a bug in certbot
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 16, 2019, 6:37pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/13 "2019-05-16T18:37:17Z")
Here is the command I used:
certbot --apache -d kekschen.eu -d www.kekschen.eu
and
certbot --apache -d kekschen.eu
(both not working)
Here is my enabled conf:
\
ServerAdmin Philipp@PNG.Services
ServerName kekschen.eu
ServerAlias www.kekschen.eu
```
DocumentRoot /var/www/kekschen/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
```
\
AllowOverride All
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 16, 2019, 10:22pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/14 "2019-05-16T22:22:35Z")
I have no idea what to do anymore. I deleted the folder /etc/letsencrypt because I thought it is releated to the problem but after running certbot I get the same error. It seems that there is a huge bug in certbot. My conf is like you said:
```
ServerAdmin Philipp@PNG.Services
ServerName kekschen.eu
ServerAlias www.kekschen.eu
DocumentRoot /var/www/kekschen/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
AllowOverride All
```
The command I try to execute
certbot --apache -d png.services -d www.png.services -d kekschen.eu -d www.kekschen.eu -d config.png.services
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 23, 2019, 7:43pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/15 "2019-05-23T19:43:28Z")
Hi Jürgen,
sorry that I reply again, but have you any ideas what I can do? The only idea I have is to reinstall Ubuntu which would take a long time.
---
### Author:  [@jmorahan](https://community.letsencrypt.org/u/jmorahan)
#### Post date: [May 23, 2019, 8:17pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/16 "2019-05-23T20:17:11Z")
> [@JuergenAuer](#):
>
> > ```nohighlight
> >
> >
> > ```
>
> This isn’t a place used with a domain name. Use
>
> ```nohighlight
>
>
> ```
Did you do this for _all_ your virtual hosts, or just that one? I think certbot used to get confused if you mixed the two - not sure if that issue still exists in 0.31 but it might be worth changing to `` everywhere, if you haven't already.
> [@Philipp97714](#):
>
> I deleted the folder /etc/letsencrypt
That's unfortunate, because while it wasn't installed correctly, you _had_ a certificate which you could have installed manually. Oh well - hopefully you can get another one 🙂
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [May 24, 2019, 8:07am UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/17 "2019-05-24T08:07:42Z")
I changed all virtual hosts to \*:80 but it doesn’t solve the issue. I also got new certificates in the certbot dir but again they couldn’t be installed. I don’t understand the problem. I deleted everything: the certbot dir and I cleaned up all virtual host files but however it isn’t working. Somewhere there must be a broken file on my server remaining that confuses certbot. I don’t know why it isn’t working but I think the issue would be solved if I reinstalled ubuntu - but that sholdn’t be the only solution.
---
### Author:  [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)
#### Post date: [May 24, 2019, 8:41am UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/18 "2019-05-24T08:41:53Z")
Rechecked your domain - [https://check-your-website.server-daten.de/?q=kekschen.eu](https://check-your-website.server-daten.de/?q=kekschen.eu)
port 443 answers, but sends http content.
But the content is very untypical:
> [http://kekschen.eu:443/](http://kekschen.eu:443/)
## Not Implemented
The URL or IP you are trying to access is out of service.
So create a correct vHost port 443 manual -\> documentation.
---
### Author:  [@Philipp97714](https://community.letsencrypt.org/u/Philipp97714)
#### Post date: [June 6, 2019, 12:48pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/19 "2019-06-06T12:48:46Z")
I thougt cerbot creates the vHost for SSL by its self?
---
### Author:  [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)
#### Post date: [June 6, 2019, 1:22pm UTC](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731/20 "2019-06-06T13:22:23Z")
> [@Philipp97714](#):
>
> cerbot creates the vHost for SSL by its self?
But there is a working port 80 vHost required. So Certbot can use that as template.
[Next page](https://community.letsencrypt.org/t/bug-could-not-reverse-map-the-https-virtualhost-to-the-original/93731.md?page=2)