SSL issues

Issues related to applications and software problems
unematt
Posts: 7
Joined: 2017/10/16 18:14:36

SSL issues

Postby unematt » 2017/10/18 21:04:57

Hello, I am about to pull my hair out trying to solve this ssl issue!! I have a SSL cert from comodo and I've installed it in /etc/pki/tls. I've added the entries into the vhost file for my site but when its enabled, I get SSL Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no certificate assigned. I've checked the cert and they key matches the crt file and the MD5 hash.

Any help would be awesome!!

httpd.conf:

Code: Select all

ServerRoot "/opt/rh/httpd24/root/etc/httpd"
Listen 80
#Listen 443
Include conf.modules.d/*.conf
User apache
Group apache
ServerAdmin root@localhost
DocumentRoot "/opt/rh/httpd24/root/var/www/html"
<Directory "/opt/rh/httpd24/root/var/www">
Options +SymLinksIfOwnerMatch
    AllowOverride all
    # Allow open access:
    Require all granted
</Directory>

# Further relax access to the default document root:
<Directory "/opt/rh/httpd24/root/var/www/html">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks
Options +SymLinksIfOwnerMatch
    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride all

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
    <IfModule dir_module>
    DirectoryIndex index.php index.html index.htm home.html home.htm
    <Files ".ht*">
    Require all denied
</Files>
</IfModule>
</Directory>
ErrorLog "logs/error_log"
LogLevel warn

<IfModule log_config_module>
    #
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    #
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>

    #
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    #
    #CustomLog "logs/access_log" common

    #
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #
    CustomLog "logs/access_log" combined
</IfModule>
<IfModule alias_module>
ScriptAlias /cgi-bin/ "/opt/rh/httpd24/root/var/www/cgi-bin/"

</IfModule>
<Directory "/opt/rh/httpd24/root/var/www/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
</Directory>
<IfModule mime_module>
TypesConfig /etc/mime.types
 AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
 AddType text/html .shtml
    AddOutputFilter INCLUDES .shtml
</IfModule>
AddDefaultCharset UTF-8

<IfModule mime_magic_module>
    #
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type.  The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #
    MIMEMagicFile conf/magic
</IfModule>
EnableSendfile on

# Supplemental configuration
#
# Load config files in the "/etc/httpd/conf.d" directory, if any.
IncludeOptional conf.d/*.conf


vhost.conf:

Code: Select all

<Directory /usr/share/www>
        AllowOverride All
        Options FollowSymLinks
        Require all granted
        Order deny,allow
        Allow from all
<IfVersion < 2.4>
    Allow from all
</IfVersion>
<IfVersion >= 2.4>
    Require all granted
</IfVersion>
        # rewrite for backward compability of public links
        RedirectMatch "^/pydio_public/(.*)" "/pydio/public/$1"
</Directory>

<VirtualHost files.bencor.info:80>
        DocumentRoot "/usr/share/www"
        ServerName test.bencor.info
</VirtualHost>
<VirtualHost files.bencor.info:443>
        ServerName files.bencor.info
        ServerAdmin massimo.mucci@bencorinc.com
####### HOME PAGE: PYDIO #######
#       SSLEngine on
        SSLCertificateFile /etc/pki/tls/files_bencor_info.crt
        SSLCertificateKeyFile /etc/pki/tls/files_bencor_info.key
        SSLCertificateChainFile /etc/pki/tls/files_bencor_info.ca-bundle
        DocumentRoot /usr/share/www
        ErrorLog logs/rd_error_log
        TransferLog logs/rd_access_log
</VirtualHost>


Error:
[Wed Oct 18 15:23:48.663773 2017] [ssl:emerg] [pid 22528] AH02572: Failed to configure at least one certificate and key for files.bencor.info:443
[Wed Oct 18 15:23:48.663870 2017] [ssl:emerg] [pid 22528] SSL Library Error: error:140A80B1:SSL routines:SSL_CTX_check_private_key:no certificate assigned

Sorry for the long post, I know the config is a bit messy. I'm not sure if I've missed something small or not..

User avatar
avij
Forum Moderator
Posts: 2141
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland
Contact:

Re: SSL issues

Postby avij » 2017/10/18 21:24:38

You have SSLEngine on commented out. Perhaps you should try enabling that.

unematt
Posts: 7
Joined: 2017/10/16 18:14:36

Re: SSL issues

Postby unematt » 2017/10/18 21:45:57

I have that disabled so that apache starts. This site is up currently.

unematt
Posts: 7
Joined: 2017/10/16 18:14:36

Re: SSL issues

Postby unematt » 2017/10/19 13:36:04

Also, heres the ssl.conf:

Code: Select all

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

##
##  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:/opt/rh/httpd24/root/var/run/httpd/sslcache(512000)
SSLSessionCacheTimeout  300

#   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 HIGH:MEDIUM:!aNULL:!MD5

#   Speed-optimized SSL Cipher configuration:
#   If speed is your main concern (on busy HTTPS servers e.g.),
#   you might want to force clients to specific, performance
#   optimized ciphers. In this case, prepend those ciphers
#   to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
#   Caveat: by giving precedence to RC4-SHA and AES128-SHA
#   (as in the example below), most connections will no longer
#   have perfect forward secrecy - if the server's key is
#   compromised, captures of past or future traffic must be
#   considered compromised, too.
#SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
#SSLHonorCipherOrder on

#   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/ssl/certs/files_bencor_info.crt

#   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/ssl/certs/bencor.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/ssl/certs/files_bencor_info.ca-bundle ***

#   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/ssl/certs/files_bencor_info.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.
BrowserMatch "MSIE [2-5]" \
         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>                   


I left some things commented out as I have them in the vhost file.

dcrdev
Posts: 54
Joined: 2015/10/25 23:42:17

Re: SSL issues

Postby dcrdev » 2017/10/19 14:49:29

The certificates you placed in /etc/pki/tls, did you copy them in there or move them? If the latter it's likely you are using the incorrect selinux context; which would be an issue if you have selinux enabled.

Use the following to fix it:

Code: Select all

restorecon -Rv


Also your private key should really be in:

Code: Select all

/etc/pki/tls/private


Your certs in:

Code: Select all

/etc/pki/tls/certs


Have you checked the permissions on both the private key and certificate, does the apache user have read access on them?

Other than that, would be helpful if you could provide a full log and also the output of:

Code: Select all

systemctl status httpd -l

unematt
Posts: 7
Joined: 2017/10/16 18:14:36

Re: SSL issues

Postby unematt » 2017/10/19 15:04:36

I have SELinux disabled currently.

I moved the certs and keys into the locations you suggested and checked the permissions.

Code: Select all

[root@files tls]# ls -ls private/
total 8
4 -rwx------  1 apache apache 1704 Oct 18 10:27 files_bencor_info.key
4 -rw-------. 1 apache apache 1675 Mar  1  2017 localhost.key
[root@files tls]# ls -ls certs/
total 28
0 lrwxrwxrwx  1 apache apache   49 Mar  1  2017 ca-bundle.crt -> /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
0 lrwxrwxrwx  1 apache apache   55 Mar  1  2017 ca-bundle.trust.crt -> /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt
8 -rwx------  1 apache apache 4111 Feb 11  2014 files_bencor_info.ca-bundle
4 -rwx------  1 apache apache 2057 Oct 18 00:00 files_bencor_info.crt
0 drwx------  2 apache apache   85 Oct 18 10:25 keys.old
4 -rwx------. 1 apache apache 1468 Mar  1  2017 localhost.crt
4 -rwx------  1 apache apache  610 Aug  4 01:41 make-dummy-cert
4 -rwx------  1 apache apache 2516 Aug  4 01:41 Makefile
4 -rwx------  1 apache apache  829 Aug  4 01:41 renew-dummy-cert


Heres what systemctl says:

Code: Select all

[root@files httpd]# systemctl status httpd24-httpd -l
● httpd24-httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd24-httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2017-10-19 09:52:17 CDT; 11s ago
  Process: 34588 ExecStop=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -k graceful-stop (code=exited, status=0/SUCCESS)
  Process: 34586 ExecStart=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 34586 (code=exited, status=1/FAILURE)

Oct 19 09:52:16 files.bencor.info systemd[1]: Starting The Apache HTTP Server...
Oct 19 09:52:16 files.bencor.info systemd[1]: httpd24-httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 19 09:52:17 files.bencor.info httpd-scl-wrapper[34588]: httpd (no pid file) not running
Oct 19 09:52:17 files.bencor.info systemd[1]: Failed to start The Apache HTTP Server.
Oct 19 09:52:17 files.bencor.info systemd[1]: Unit httpd24-httpd.service entered failed state.
Oct 19 09:52:17 files.bencor.info systemd[1]: httpd24-httpd.service failed.


Uncommenting and adding the certs in the ssl.conf gave a different error:

Code: Select all

[root@files httpd]# systemctl status httpd24-httpd -l
● httpd24-httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd24-httpd.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2017-10-19 09:47:02 CDT; 6s ago
  Process: 34433 ExecStop=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -k graceful-stop (code=exited, status=1/FAILURE)
  Process: 34431 ExecStart=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 34431 (code=exited, status=1/FAILURE)

Oct 19 09:47:02 files.bencor.info systemd[1]: Starting The Apache HTTP Server...
Oct 19 09:47:02 files.bencor.info httpd-scl-wrapper[34431]: AH00526: Syntax error on line 116 of /opt/rh/httpd24/root/etc/httpd/conf.d/ssl.conf:
Oct 19 09:47:02 files.bencor.info httpd-scl-wrapper[34431]: SSLCertificateChainFile takes one argument, SSL Server CA Certificate Chain file ('/path/to/file' - PEM encoded)
Oct 19 09:47:02 files.bencor.info systemd[1]: httpd24-httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 19 09:47:02 files.bencor.info httpd-scl-wrapper[34433]: AH00526: Syntax error on line 116 of /opt/rh/httpd24/root/etc/httpd/conf.d/ssl.conf:
Oct 19 09:47:02 files.bencor.info httpd-scl-wrapper[34433]: SSLCertificateChainFile takes one argument, SSL Server CA Certificate Chain file ('/path/to/file' - PEM encoded)
Oct 19 09:47:02 files.bencor.info systemd[1]: httpd24-httpd.service: control process exited, code=exited status=1
Oct 19 09:47:02 files.bencor.info systemd[1]: Failed to start The Apache HTTP Server.
Oct 19 09:47:02 files.bencor.info systemd[1]: Unit httpd24-httpd.service entered failed state.
Oct 19 09:47:02 files.bencor.info systemd[1]: httpd24-httpd.service failed.


dcrdev wrote:The certificates you placed in /etc/pki/tls, did you copy them in there or move them? If the latter it's likely you are using the incorrect selinux context; which would be an issue if you have selinux enabled.

Use the following to fix it:

Code: Select all

restorecon -Rv


Also your private key should really be in:

Code: Select all

/etc/pki/tls/private


Your certs in:

Code: Select all

/etc/pki/tls/certs


Have you checked the permissions on both the private key and certificate, does the apache user have read access on them?

Other than that, would be helpful if you could provide a full log and also the output of:

Code: Select all

systemctl status httpd -l

dcrdev
Posts: 54
Joined: 2015/10/25 23:42:17

Re: SSL issues

Postby dcrdev » 2017/10/19 15:12:43

Ok so now we're getting somewhere:

  • You have "***" at the end of SSLCertificateChainFile on line 116
  • Are you're certificates pem encoded? If not: openssl x509 -inform der -in files_bencor_info.crt -out files_bencor_info.pem

unematt
Posts: 7
Joined: 2017/10/16 18:14:36

Re: SSL issues

Postby unematt » 2017/10/19 15:43:52

I think they are PEM encoded, but no .pem file.

When I tried to encode them I got:

Code: Select all

[root@files certs]#  openssl x509 -inform der -in files_bencor_info.crt -out files_bencor_info.pem
unable to load certificate
140134402181024:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1199:
140134402181024:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:374:Type=X509

dcrdev
Posts: 54
Joined: 2015/10/25 23:42:17

Re: SSL issues

Postby dcrdev » 2017/10/19 15:46:47

Ok can you run cat on the certificate and post the output here - obviously remove the actual encoded certificate portion; I'm just interested in the headers.

BTW did you check line 116? It shouldn't have "***" at the end of it.

unematt
Posts: 7
Joined: 2017/10/16 18:14:36

Re: SSL issues

Postby unematt » 2017/10/19 15:57:13

Yes, I removed the ***

I just tried leaving the SSLCertificateChainFile /etc/pki/tls/files_bencor_info.ca-bundle commented out

Code: Select all

Oct 19 10:45:07 files.bencor.info httpd-scl-wrapper[35321]: AH00526: Syntax error on line 100 of /opt/rh/httpd24/root/etc/httpd/conf.d/ssl.conf:
Oct 19 10:45:07 files.bencor.info httpd-scl-wrapper[35321]: SSLCertificateFile: file '/etc/pki/tls/files_bencor_info.crt' does not exist or is empty
Oct 19 10:45:07 files.bencor.info systemd[1]: httpd24-httpd.service: main process exited, code=exited, status=1/FAILURE
Oct 19 10:45:07 files.bencor.info httpd-scl-wrapper[35323]: AH00526: Syntax error on line 100 of /opt/rh/httpd24/root/etc/httpd/conf.d/ssl.conf:
Oct 19 10:45:07 files.bencor.info httpd-scl-wrapper[35323]: SSLCertificateFile: file '/etc/pki/tls/files_bencor_info.crt' does not exist or is empty
Oct 19 10:45:07 files.bencor.info systemd[1]: httpd24-httpd.service: control process exited, code=exited status=1


I know the file is not empty as I compared the files when talking to comodo about the cert issue.

The crt file has:

Code: Select all

[root@files httpd]# cat /etc/pki/tls/certs/files_bencor_info.crt
-----BEGIN CERTIFICATE-----
Blah Blah

-----END CERTIFICATE-----


The ca-bundle file has the same contents but twice, including the begin cert header.