ssl issues - no certificate configured

Noah noah-list at
Sun Jun 21 03:14:35 UTC 2015

Hi List,

I am getting the following in my log (below) when starting apache.  I am 
not clear why since i have ssl certs defined in 

Verified default-ssl.conf is enabled and so is the ssl mod.

What am I doing wrong?

--- snip ---

[Sat Jun 20 23:55:47.151064 2015] [ssl:emerg] [pid 26495] AH02240: 
Server should be SSL-aware but has no certificate configured [Hint: 
SSLCertificateFile] ((null):0)
[Sat Jun 20 23:55:47.151132 2015] [ssl:emerg] [pid 26495] AH02312: Fatal 
error initialising mod_ssl, exiting.

--- snip ---

/etc/apache2/sites-available $ a2ensite default-ssl.conf
Site default-ssl already enabled

/etc/apache2/sites-available $ sudo a2enmod ssl
Considering dependency setenvif for ssl:
Module setenvif already enabled
Considering dependency mime for ssl:
Module mime already enabled
Considering dependency socache_shmcb for ssl:
Module socache_shmcb already enabled
Module ssl already enabled

/etc/apache2/sites-available $ ls -l 
lrwxrwxrwx 1 root 35 Jun 20 23:33 
/etc/apache2/sites-enabled/default-ssl.conf -> 

Cert files are there
/etc/apache2/sites-available $ wc -l /etc/apache2/ssl/apache.crt
24 /etc/apache2/ssl/apache.crt
/etc/apache2/sites-available $ wc -l /etc/apache2/ssl/apache.key
28 /etc/apache2/ssl/apache.key

-- /etc/apache2/sites-enabled/default-ssl.conf ---

cat /etc/apache2/sites-enabled/default-ssl.conf
<IfModule mod_ssl.c>
     <VirtualHost _default_:443>
         ServerAdmin webmaster at localhost

         DocumentRoot /var/www/html

         # Available loglevels: trace8, ..., trace1, debug, info, 
notice, warn,
         # error, crit, alert, emerg.
         # It is also possible to configure the loglevel for particular
         # modules, e.g.
         #LogLevel info ssl:warn

         ErrorLog ${APACHE_LOG_DIR}/error.log
         CustomLog ${APACHE_LOG_DIR}/access.log combined

         # For most configuration files from conf-available/, which are
         # enabled or disabled at a global level, it is possible to
         # include a line for only one particular virtual host. For 
example the
         # following line enables the CGI configuration for this host only
         # after it has been globally disabled with "a2disconf".
         #Include conf-available/serve-cgi-bin.conf

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

         #   A self-signed (snakeoil) certificate can be created by 
         #   the ssl-cert package. See
         #   /usr/share/doc/apache2/README.Debian.gz for more info.
         #   If both key and certificate are stored in the same file, 
only the
         #   SSLCertificateFile directive is needed.
#        SSLCertificateFile    /etc/ssl/certs/ssl-cert-snakeoil.pem
#        SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
         SSLCertificateFile /etc/apache2/ssl/apache.crt
         SSLCertificateKeyFile /etc/apache2/ssl/apache.key

         #   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/apache2/ssl.crt/server-ca.crt

         #   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)
         #   Note: Inside SSLCACertificatePath you need hash symlinks
         #         to point to the certificate files. Use the provided
         #         Makefile to update the hash symlinks after changes.
         #SSLCACertificatePath /etc/ssl/certs/
         #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

         #   Certificate Revocation Lists (CRL):
         #   Set the CA revocation path where to find CA CRLs for client
         #   authentication or alternatively one huge file containing all
         #   of them (file must be PEM encoded)
         #   Note: Inside SSLCARevocationPath you need hash symlinks
         #         to point to the certificate files. Use the provided
         #         Makefile to update the hash symlinks after changes.
         #SSLCARevocationPath /etc/apache2/ssl.crl/
         #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

         #   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

         #   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 
         #     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_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 
         #     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 OptRenegotiate:
         #     This enables optimized SSL connection renegotiation 
handling when SSL
         #     directives are used in per-directory context.
         #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
         <FilesMatch "\.(cgi|shtml|phtml|php)$">
                 SSLOptions +StdEnvVars
         <Directory /usr/lib/cgi-bin>
                 SSLOptions +StdEnvVars

         #   SSL Protocol Adjustments:
         #   The safe and default but still SSL/TLS standard compliant 
         #   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 
         #     works correctly.
         #   Notice: Most problems of broken clients are also related to 
the HTTP
         #   keep-alive facility, so you usually additionally want to 
         #   keep-alive for those clients, too. Use variable 
"nokeepalive" for this.
         #   Similarly, one has to force some clients to use HTTP/1.0 to 
         #   their broken HTTP/1.1 implementation. Use variables 
"downgrade-1.0" and
         #   "force-response-1.0" for this.
         BrowserMatch "MSIE [2-6]" \
                 nokeepalive ssl-unclean-shutdown \
                 downgrade-1.0 force-response-1.0
         # MSIE 7 and newer should be able to use keepalive
         BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown


-- snip ---

More information about the ubuntu-users mailing list