VirtualHost overlap on port 443 localhost.localdomain

Help
#1

https://crt.sh/?q=deepmatrix.net

ran certonly

Centos 6 64-bit Apache with Zpanel
Root Access.

I know whats wrong but I don’t know how to fix it…

I’m not in the server very often.
I used certonly and went the manual way.
The certificates have installed and all seems good there.

When I restarted apache I got an warning. and my sites says
Your connection is not secure.
(Ive read many posts nothing I found seems to fit my issue)

Did a search found this command to repeat what the warning is.

httpd -t -D DUMP_VHOSTS
[Thu Nov 09 12:45:44 2017] [warn] default VirtualHost overlap on port 443, the first has precedence
VirtualHost configuration:
wildcard NameVirtualHosts and default servers:
default:443 localhost.localdomain (/etc/httpd/conf.d/ssl.conf:74)
*:443 deepmatrix.net (/etc/zpanel/configs/apache/zpanel-ssl-vhost.conf:5)

and this command
grep -ir 443 /etc/httpd/conf*
/etc/httpd/conf.d/ssl.conf:Listen 443
/etc/httpd/conf.d/ssl.conf:
/etc/httpd/conf.d/ssl.conf:#ServerName www.example.com:443

The first that has precedence was default on the server install or I may have turned it on.
example.com localhost.localdomain

httpd.conf has an include directive for Zpanel:

Include /etc/zpanel/configs/apache/httpd.conf

Then… /etc/zpanel/configs/apache/httpd.conf has an include directive for the
automatically generated vhosts file (generated and can not be edited)
I added a custom include for letsEncrypt.

###################################################################

Now we include the generic VHOST configuration file that holds all the ZPanel user hosted vhost data

Include /etc/zpanel/configs/apache/httpd-vhosts.conf

#CUSTOM SSL LetsEncrypt CONFIGURATION
Include /etc/zpanel/configs/apache/zpanel-ssl-vhost.conf
###################################################################

my custom ssl include contained more domains. I removed all them and have left one.
I made this file by various examples in this forum

########################################################################
#Custom include for SSL LetsEncrypt
#ONLY EDIT THIS FILE

DOMAIN: deepmatrix.net

<virtualhost *:443>
ServerName deepmatrix.net
ServerAlias deepmatrix.net www.deepmatrix.net
ServerAdmin
DocumentRoot “/var/zpanel/hostdata/zadmin/public_html/deepmatrix_net”

SSLEngine on
SSLCertificateFile "/etc/letsencrypt/live/deepmatrix.net/cert.pem"
SSLCertificateChainFile "/etc/letsencrypt/live/deepmatrix.net/chain.pem"
SSLCertificateKeyFile “/etc/letsencrypt/live/deepmatrix.net/privkey.pem”

SSLProtocol all -SSLv2 -SSLv3
SSLHonorCipherOrder on
SSLProtocol all -SSLv2 -SSLv3
SSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-CM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256$

Redirect permanent / https://deepmatrix.net/

#End domain deepmatrix.net
##########################################################################

How do I remove the default ssl so letEncrypt it holds precedence?

#2

If you could show more or all of these two files maybe we can advise:
/etc/httpd/conf.d/ssl.conf
/etc/zpanel/configs/apache/zpanel-ssl-vhost.conf

1 Like
#3

Thank you for your reply

I have managed to get the certificates working on https BUT now
https://deepmatrix.net is now loading the websites control panel instead
of the default index file.
All the domains that I added when I did certonly are also showing green lock and are pointing to
the default control panel instead of the sites main home page
. I haven’t even added these other domains into zpanel-ssl-vhost.conf yet. ???
eg. https://pixpile.com

I realised the /etc/httpd/conf.d/ssl.conf had a problem
I dont know how to copy the contents of the file using Nano (Its a long file)
Is there a trick???
I identified 3 places in the file to edit the ssl.conf and add the letsencrypt path
/etc/httpd/conf.d/ssl.conf

This added into the path other than the new problems this bit is now fine.

I added the letsEcrypty path into /etc/httpd/conf.d/ssl.conf
############################################################
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt
SSLCertificateChainFile /etc/letsencrypt/live/deepmatrix.net/chain.pem
##############################################################

the contents of /etc/zpanel/configs/apache/zpanel-ssl-vhost.conf is above posted in my original help request.
starts at #Custom include for SSL LetsEncrypt

I have commented out the line
Redirect permanent / https://deepmatrix.net/
as all the sites(not just deepmatrix.net) were being redirected to https: and to control panel page instead of main home page.

I did the cerbot-only certonly. I was sure the webroot path was correct
/var/zpanel/hostdata/zadmin/public_html/deepmatrix_net.

I agree with the web being encrypted. But geez, I’ve been stuffing around with this for a week.
It would make more sense if the browsers served all documents encrypted.

#4

try:
more /etc/httpd/conf.d/ssl.conf
more /etc/zpanel/configs/apache/zpanel-ssl-vhost.conf

1 Like
#5

/etc/httpd/conf.d/ssl.conf

#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailing information about these
# directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html>
#
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned.
#

LoadModule ssl_module modules/mod_ssl.so

#
# When we also provide SSL we have to listen to the
# the HTTPS port in addition.
#
Listen 443

##
##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.
##

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is a internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog  builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism
#   to use and second the expiring timeout (in seconds).
SSLSessionCache         shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout  300

#   Semaphore:
#   Configure the path to the mutual exclusion semaphore the
#   SSL engine uses internally for inter-process synchronization.
SSLMutex default

#   Pseudo Random Number Generator (PRNG):
#   Configure one or more sources to seed the PRNG of the
#   SSL library. The seed data should be of good random quality.
#   WARNING! On some platforms /dev/random blocks if not enough entropy
#   is available. This means you then cannot use the /dev/random device
#   because it would lead to very long connection times (as long as
#   it requires to make more entropy available). But usually those
#   platforms additionally provide a /dev/urandom device which doesn't
#   block. So, if available, use this one instead. Read the mod_ssl User
#   Manual for more details.
SSLRandomSeed startup file:/dev/urandom  256
SSLRandomSeed connect builtin
#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512

#
# Use "SSLCryptoDevice" to enable any supported hardware
# accelerators. Use "openssl engine -v" to list supported
# engine names.  NOTE: If you enable an accelerator and the
# server does not start, consult the error logs and ensure
# your accelerator is functioning properly.
#
SSLCryptoDevice builtin
#SSLCryptoDevice ubsec

##
## SSL Virtual Host Context
##

<VirtualHost _default_:443>

# General setup for the virtual host, inherited from global configuration
#DocumentRoot "/var/www/html"
#ServerName www.example.com:443

# Use separate log files for the SSL virtual host; note that LogLevel
# is not inherited from httpd.conf.
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn

#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on

#   SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect.  Disable SSLv2 access by default:
SSLProtocol all -SSLv2

#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite DEFAULT:!EXP:!SSLv2:!DES:!IDEA:!SEED:+3DES

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
#SSLCertificateFile /etc/pki/tls/certs/localhost.crt
SSLCertificateFile /etc/letsencrypt/live/deepmatrix.net/cert.pem

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
#SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
SSLCertificateKeyFile /etc/letsencrypt/live/deepmatrix.net/privkey.pem

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt
SSLCertificateChainFile /etc/letsencrypt/live/deepmatrix.net/chain.pem

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
#SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt

#   Client Authentication (Type):
#   Client certificate verification type and depth.  Types are
#   none, optional, require and optional_no_ca.  Depth is a
#   number which specifies how deeply to verify the certificate
#   issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth  10

#   Access Control:
#   With SSLRequire you can do per-directory access control based
#   on arbitrary complex boolean expressions containing server
#   variable checks and other lookup directives.  The syntax is a
#   mixture between C and Perl.  See the mod_ssl documentation
#   for more details.
#<Location />
#SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
#            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
#            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
#            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
#            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
#           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>

#   SSL Engine Options:
#   Set various options for the SSL engine.
#   o FakeBasicAuth:
#     Translate the client X.509 into a Basic Authorisation.  This means that
#     the standard Auth/DBMAuth methods can be used for access control.  The
#     user name is the `one line' version of the client's X.509 certificate.
#     Note that no password is obtained from the user. Every entry in the user
#     file needs this password: `xxj31ZMTZzkVA'.
#   o ExportCertData:
#     This exports two additional environment variables: SSL_CLIENT_CERT and
#     SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
#     server (always existing) and the client (only existing when client
#     authentication is used). This can be used to import the certificates
#     into CGI scripts.
#   o StdEnvVars:
#     This exports the standard SSL/TLS related `SSL_*' environment variables.
#     Per default this exportation is switched off for performance reasons,
#     because the extraction step is an expensive operation and is usually
#     useless for serving static content. So one usually enables the
#     exportation for CGI and SSI requests only.
#   o StrictRequire:
#     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
#     under a "Satisfy any" situation, i.e. when it applies access is denied
#     and no other module can change it.
#   o OptRenegotiate:
#     This enables optimized SSL connection renegotiation handling when SSL
#     directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<Files ~ "\.(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
</Files>
<Directory "/var/www/cgi-bin">
    SSLOptions +StdEnvVars
</Directory>

#   SSL Protocol Adjustments:
#   The safe and default but still SSL/TLS standard compliant shutdown
#   approach is that mod_ssl sends the close notify alert but doesn't wait for
#   the close notify alert from client. When you need a different shutdown
#   approach you can use one of the following variables:
#   o ssl-unclean-shutdown:
#     This forces an unclean shutdown when the connection is closed, i.e. no
#     SSL close notify alert is send or allowed to received.  This violates
#     the SSL/TLS standard but is needed for some brain-dead browsers. Use
#     this when you receive I/O errors because of the standard approach where
#     mod_ssl sends the close notify alert.
#   o ssl-accurate-shutdown:
#     This forces an accurate shutdown when the connection is closed, i.e. a
#     SSL close notify alert is send and mod_ssl waits for the close notify
#     alert of the client. This is 100% SSL/TLS standard compliant, but in
#     practice often causes hanging connections with brain-dead browsers. Use
#     this only for browsers where you know that their SSL implementation
#     works correctly.
#   Notice: Most problems of broken clients are also related to the HTTP
#   keep-alive facility, so you usually additionally want to disable
#   keep-alive for those clients, too. Use variable "nokeepalive" for this.
#   Similarly, one has to force some clients to use HTTP/1.0 to workaround
#   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
#   "force-response-1.0" for this.
SetEnvIf User-Agent ".*MSIE.*" \
         nokeepalive ssl-unclean-shutdown \
         downgrade-1.0 force-response-1.0

#   Per-Server Logging:
#   The home of a custom SSL log file. Use this when you want a
#   compact non-error SSL logfile on a virtual host basis.
CustomLog logs/ssl_request_log \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

</VirtualHost>


/etc/zpanel/configs/apache/zpanel-ssl-vhost.conf
#Custom include for SSL LetsEncrypt
#ONLY EDIT THIS FILE

# DOMAIN: deepmatrix.net
<virtualhost *:443>
ServerName deepmatrix.net
ServerAlias deepmatrix.net www.deepmatrix.net
ServerAdmin 
DocumentRoot "/var/zpanel/hostdata/zadmin/public_html/deepmatrix_net"

SSLEngine on
SSLCertificateFile "/etc/letsencrypt/live/deepmatrix.net/cert.pem"
SSLCertificateChainFile "/etc/letsencrypt/live/deepmatrix.net/chain.pem"
SSLCertificateKeyFile "/etc/letsencrypt/live/deepmatrix.net/privkey.pem"

SSLProtocol             all -SSLv2 -SSLv3
SSLHonorCipherOrder on
SSLProtocol all -SSLv2 -SSLv3
SSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-R
SA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE
-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SH
A256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-E
CDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SH
A256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES2
56-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES2
56-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:
!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES
-CBC3-SHA


#Redirect permanent / https://deepmatrix.net/
</VirtualHost>

#End domain deepmatrix.net
##########################################################################
#6

The first file is difficult to read.
But I think the problem may be in there.
Please show:
grep -ri ‘servername|serveralias’ /etc/httpd/conf.d/

#7

I got -bash: serveralias’: command not found

#8

try double quotes
grep -ri “servername|serveralias” /etc/httpd/conf.d/
and/or backslash before |
grep -ri “servername\|serveralias” /etc/httpd/conf.d/

#9

This
grep -ri “servername|serveralias” /etc/httpd/conf.d/
and this
grep -ri “servername|serveralias” /etc/httpd/conf.d/

just went to the prompt with no error and showed nothing

#10

I can do this.
grep -ir 443 /etc/httpd/conf*
/etc/httpd/conf.d/ssl.conf.save.1:Listen 443
/etc/httpd/conf.d/ssl.conf.save.1:
/etc/httpd/conf.d/ssl.conf.save.1:#ServerName www.example.com:443
/etc/httpd/conf.d/ssl.conf:Listen 443
/etc/httpd/conf.d/ssl.conf:
/etc/httpd/conf.d/ssl.conf:#ServerName www.example.com:443
/etc/httpd/conf.d/ssl.conf.save:Listen 443

the servername example.com is commented out

#11

OK try them independently:
grep -ri servername /etc/httpd/conf.d/
then
grep -ri serveralias /etc/httpd/conf.d/

#12

first one worked

grep -ri servername /etc/httpd/conf.d/
/etc/httpd/conf.d/ssl.conf.save.1:#ServerName www.example.com:443
/etc/httpd/conf.d/ssl.conf:#ServerName www.example.com:443

grep -ri serveralias /etc/httpd/conf.d/
no error just command prompt

#13

OK.
/etc/httpd/conf.d/ssl.conf
has only one ServerName line and it’s now commented out (#ServerName)
I’m not sure of the default behavior when there is no ServerName … but it can’t be what you wanted.

It also uses:
SSLCertificateFile /etc/letsencrypt/live/deepmatrix.net/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/deepmatrix.net/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/deepmatrix.net/chain.pem
So it is setup to be a name in the cert /etc/letsencrypt/live/deepmatrix.net/cert.pem

#14

I think, you should get rid of /etc/httpd/conf.d/ssl.conf since configuration is done in /etc/zpanel/configs/apache/zpanel-ssl-vhost.conf:

mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled

Then try to restart Apache.

2 Likes
#15

I see that example.com is commented out
I added the letsencrypt path to the ssl.conf file.

What is the Server Name?
Does it have to be .com or .net
Could the server be called just a word?

the http versions are pointing to the main index pages.
the https are pointing to the control panel.

Zpanel has been renamed to Sentora,
I’ve been searching everywhere. Not much info on LetsEncrypt for Zpanel

#16

ok will try
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.disabled

#17

restart failed:

service httpd restart
Stopping httpd: [ OK ]
Starting httpd: Syntax error on line 11 of /etc/zpanel/configs/apache/zpanel-ssl-vhost.conf:
Invalid command ‘SSLEngine’, perhaps misspelled or defined by a module not included in the server configuration
[FAILED]

#18

@QuantumFlux OK, try to put these lines into /etc/httpd/conf.d/ssl.conf:

LoadModule ssl_module modules/mod_ssl.so
Listen 443
SSLPassPhraseDialog builtin
SSLSessionCache shmcb:/var/cache/mod_ssl/scache(512000)
SSLSessionCacheTimeout 300
SSLRandomSeed startup file:/dev/urandom 256
SSLRandomSeed connect builtin

This will basically setup mod_ssl without the default virtual host.
Then restart apache.

#19

Those lines are already in the ssl.conf

#20

I thought you renamed the file?
You may also edit ssl.conf and delete everything including and below the first <VirtualHost> , that would be the same result.

Please note: the filename has to be ssl.conf, not ssl.conf.anything because this won’t be included from the main Apache configuration file.