Two domains mapped to the same IP

aminemarref · August 26, 2021, 4:27pm

This is it:

<IfModule mod_ssl.c>
<VirtualHost *:443>
  ServerAdmin webmaster@localhost
  DocumentRoot ****
  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined
#  <LocationMatch "^/(?!\.well-known)">
        #send all other requests to HTTPS
#       RewriteEngine On
# Some rewrite rules in this file were disabled on your HTTPS site,
# because they have the potential to create redirection loops.
#       RewriteCond %{HTTPS} !=on
#       RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1
#  </LocationMatch>
#   RewriteCond %{SERVER_NAME} =infinity-computer-systems.com
#   RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
ServerName infinity-computer-systems.com
Include /etc/letsencrypt/options-ssl-apache.conf
ServerAlias marref.org
SSLCertificateFile /etc/letsencrypt/live/marref.org/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/marref.org/privkey.pem
</VirtualHost>

</IfModule>
<IfModule mod_ssl.c>
<VirtualHost *:80>
  ServerAdmin webmaster@localhost
  DocumentRoot ****
  ServerName marref.org
  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined
  <LocationMatch "^/(?!\.well-known)">
        #send all other requests to HTTPS
        RewriteEngine On
# Some rewrite rules in this file were disabled on your HTTPS site,
# because they have the potential to create redirection loops.
#         RewriteCond %{HTTPS} !=on
#         RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1
  </LocationMatch>
#   RewriteCond %{SERVER_NAME} =marref.org
#   RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
</IfModule>

rg305 · August 26, 2021, 4:27pm

Shouldn't that be:

aminemarref · August 26, 2021, 4:27pm

My stupid mistake: it is infinity-computer-systems.com

rg305 · August 26, 2021, 4:28pm

Ok I see what you get now:

rg305 · August 26, 2021, 4:30pm

Having these two lines in the same file created that problem:

They now have separate certs, so they need separate vhost config (in order to point each name to its' matching cert).
OR
If they really do the same thing and can be combined into one DocumentRoot, one site, one cert...
Then all we need to do is put both domain names onto one single cert.

We can do that with:
sudo certbot --apache -d "infinity-computer-systems.com,marref.org" --dry-run
[always first use --dry-run - while testing]

If the sites do different things and can't be combined, then they need separate DocumentRoots, separate vhost configs, and separate certs.

aminemarref · August 26, 2021, 4:32pm

Do I comment out the ServerAlias?

rg305 · August 26, 2021, 4:33pm

See my add to last post ^

aminemarref · August 26, 2021, 4:37pm

My system complains about the dry run:
--dry-run currently only works with the 'certonly' or 'renew' subcommands ('run')

Are you using a futuristic version?

rg305 · August 26, 2021, 4:40pm

OK fine, go without --dry-run then.

aminemarref · August 26, 2021, 4:42pm

I get this:

$ sudo certbot --apache -d "infinity-computer-systems.com,marref.org"
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
You have an existing certificate that contains a portion of the domains you
requested (ref: /etc/letsencrypt/renewal/infinity-computer-systems.com.conf)
It contains these names: infinity-computer-systems.com
You requested these names for the new certificate:
infinity-computer-systems.com, marref.org.
Do you want to expand and replace this existing certificate with the new
certificate?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(E)xpand/(C)ancel: E
Renewing an existing certificate for infinity-computer-systems.com and marref.org
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/infinity-computer-systems.com/fullchain.pem
Key is saved at:         /etc/letsencrypt/live/infinity-computer-systems.com/privkey.pem
This certificate expires on 2021-11-24.
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 infinity-computer-systems.com to /etc/apache2/sites-enabled/000-default-le-ss
l.conf
Successfully deployed certificate for marref.org to /etc/apache2/sites-enabled/000-default-le-ssl.conf
Failed redirect for infinity-computer-systems.com
Unable to set the redirect enhancement for infinity-computer-systems.com.
NEXT STEPS:
- The certificate was saved, but could not be installed (installer: apache). After fixing the error shown below, tr
y installing it again by running:
  certbot install --cert-name infinity-computer-systems.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/let
sencrypt.log or re-run Certbot with -v for more details.

rg305 · August 26, 2021, 4:44pm

Let's review the changes:
certbot certificates

And show file:

aminemarref · August 26, 2021, 4:47pm

Here we go:

$ sudo certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
  Certificate Name: infinity-computer-systems.com
    Serial Number: 407a18eb353298e4a53863774d9cdbb66e5
    Key Type: RSA
    Domains: infinity-computer-systems.com marref.org
    Expiry Date: 2021-11-24 15:40:53+00:00 (VALID: 89 days)
    Certificate Path: /etc/letsencrypt/live/infinity-computer-systems.com/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/infinity-computer-systems.com/privkey.pem
  Certificate Name: marref.org
    Serial Number: 46723b8008253bf26e6d7d610fc5fc289d4
    Key Type: RSA
    Domains: marref.org
    Expiry Date: 2021-11-24 15:10:01+00:00 (VALID: 89 days)
    Certificate Path: /etc/letsencrypt/live/marref.org/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/marref.org/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

and:

$ cat /etc/apache2/sites-enabled/000-default-le-ssl.conf
<IfModule mod_ssl.c>
<VirtualHost *:443>
  ServerAdmin webmaster@localhost
  DocumentRoot ****
  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined
#  <LocationMatch "^/(?!\.well-known)">
        #send all other requests to HTTPS
#       RewriteEngine On
# Some rewrite rules in this file were disabled on your HTTPS site,
# because they have the potential to create redirection loops.
#       RewriteCond %{HTTPS} !=on
#       RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1
#  </LocationMatch>
#   RewriteCond %{SERVER_NAME} =infinity-computer-systems.com
#   RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
ServerName infinity-computer-systems.com
Include /etc/letsencrypt/options-ssl-apache.conf
ServerAlias marref.org
SSLCertificateFile /etc/letsencrypt/live/infinity-computer-systems.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/infinity-computer-systems.com/privkey.pem
</VirtualHost>
</IfModule>
<IfModule mod_ssl.c>
<VirtualHost *:80>
  ServerAdmin webmaster@localhost
  DocumentRoot ****
  ServerName marref.org
  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined
  <LocationMatch "^/(?!\.well-known)">
        #send all other requests to HTTPS
        RewriteEngine On
# Some rewrite rules in this file were disabled on your HTTPS site,
# because they have the potential to create redirection loops.
#         RewriteCond %{HTTPS} !=on
#         RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1
  </LocationMatch>
#   RewriteCond %{SERVER_NAME} =marref.org
#   RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
</IfModule>

rg305 · August 26, 2021, 4:52pm

OK!
Here we go.
Let's remove the single domain cert:
certbot delete --cert-name marref.org

Then update file:
/etc/apache2/sites-enabled/000-default-le-ssl.conf
As follows:

<VirtualHost *:443>
  ServerName infinity-computer-systems.com
  ServerAlias marref.org
  DocumentRoot /home/marref_infcs_1/websites/marref_org
  ServerAdmin webmaster@localhost
  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined
  Include /etc/letsencrypt/options-ssl-apache.conf
  SSLCertificateFile /etc/letsencrypt/live/infinity-computer-systems.com/fullchain.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/infinity-computer-systems.com/privkey.pem
</VirtualHost>

Restart Apache and all should be good.

aminemarref · August 26, 2021, 4:59pm

And indeed it works!
Thanks a lot for your five-star support! I really appreciate it very much.

rg305 · August 26, 2021, 5:11pm

Pleased to hear that

When you do go to add another site, keep that in mind.
If it needs to be served from a different document root, then it will need a separate vhost config (and that may require using a separate cert).

In any case, Cheers from Miami

#FreeCUBA

Topic		Replies	Views
Multiple domains that share an IP address - How to Help	12	910	July 31, 2019
Bug: Could not reverse map the HTTPS VirtualHost to the original Help	29	1900	July 23, 2019
Server w/multiple domains - Wrong Cert Server	38	7260	November 4, 2017
Struggling to create a new multi-domain certificate Help	7	794	April 3, 2020
Certificate name mismatch Help	36	248	February 27, 2026

Two domains mapped to the same IP

Related topics