(.pem file locations) for AL2023 in ssl.conf

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
provision.domains

I ran this command:
No command, Please review my ssl.conf file. (It is a default of The OpenSSL system profile.)

It produced this output:
When I restarted apache, it failed. I can share that later, but first I need to know if I put your .pem files correctly in the ssl.conf file

My web server is (include version):
Lightsail
system-release-2023.3.20240131-0.amzn2023.noarch

The operating system my web server runs on is (include version):
AL2023

My hosting provider, if applicable, is:
Amazon Web Services Lightsail

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):
Used Webroot

Below is an excerpt of ssl.conf:
Please confirm I have placed your .pem files correctly.

#   The OpenSSL system profile is configured by default.  

#   Point SSLCertificateFile at a PEM encoded certificate.  If
#   the certificate is encrypted, then you will be prompted for a
#   pass phrase.  Note that restarting httpd will prompt again.  Keep
#   in mind that if you have both an RSA and a DSA certificate you
#   can configure both in parallel (to also allow the use of DSA
#   ciphers, etc.)
#   Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt)
#   require an ECC certificate which can also be configured in
#   parallel.
SSLCertificateFile /etc/letsencrypt/live/provision.domains/fullchain.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.)
#   ECC keys, when in use, can also be configured in parallel
SSLCertificateKeyFile /etc/letsencrypt/live/provision.domains/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 convenience.
SSLCertificateChainFile /etc/letsencrypt/live/provision.domains/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

You should comment that out. The full chain was included on different statement. This chain file statement was deprecated long ago in Apache

You said you had other apache systems working so maybe reviewing those would be helpful. The configurator below can also be helpful

3 Likes

Thanks very much. :slight_smile:
I will comment that out.

Sorry about all the "bold" text. I wanted to make it easier to read, but it made it worse.

Thanks for the generator link.
I lke it.

1 Like