Thank you very much. I didn't notice that. I moved the 80-to-443 redirect into another file, and the rest of www.reppep.com.conf to the end of ssl.conf. I moved the old www.reppep.com.conf file into a subdirectory where it will not load.
It looks like certbot is putting new certs into my port 80 redirect file, but not updating paths in ssl.conf.
[root@rocky conf.d]# apachectl configtest
Syntax OK
[root@rocky conf.d]# apachectl restart
[root@rocky conf.d]# ls
autoindex.conf README ssl.conf vhost.d www.reppep.com.80.conf
DISABLED rename.DIS userdir.conf welcome.conf
[root@rocky conf.d]# cat www.reppep.com.80.conf
# This vhost only redirects to HTTPS
<VirtualHost *:80>
ServerName www.reppep.com
ServerAlias www rocky rocky.reppep.com img.reppep.com img.chrispepper.com
UseCanonicalName on
# RedirectPermanent / https://rocky.reppep.com/
# RedirectPermanent / https://www.reppep.com/
CustomLog "|/usr/sbin/cronolog /var/log/httpd/%Y/%Y-%m-www-access_log" combined
RewriteEngine on
RewriteCond %{SERVER_NAME} =img.reppep.com [OR]
RewriteCond %{SERVER_NAME} =img.chrispepper.com [OR]
RewriteCond %{SERVER_NAME} =rocky.reppep.com [OR]
RewriteCond %{SERVER_NAME} =www.reppep.com [OR]
RewriteCond %{SERVER_NAME} =www [OR]
RewriteCond %{SERVER_NAME} =rocky
RewriteRule ^ https://www.reppep.com%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
[root@rocky conf.d]# cat ssl.conf
#
# When we also provide SSL we have to listen to the
# standard 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 exec:/usr/libexec/httpd-ssl-pass-dialog
# Inter-Process Session Cache:
# Configure the SSL Session Cache: First the mechanism
# to use and second the expiring timeout (in seconds).
SSLSessionCache shmcb:/run/httpd/sslcache(512000)
SSLSessionCacheTimeout 300
#
# 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
# List the protocol versions which clients are allowed to connect with.
# The OpenSSL system profile is used by default. See
# update-crypto-policies(8) for more details.
#SSLProtocol all -SSLv3
#SSLProxyProtocol all -SSLv3
# User agents such as web browsers are not configured for the user's
# own preference of either security or performance, therefore this
# must be the prerogative of the web server administrator who manages
# cpu load versus confidentiality, so enforce the server's cipher order.
SSLHonorCipherOrder on
# SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
# The OpenSSL system profile is configured by default. See
# update-crypto-policies(8) for more details.
SSLCipherSuite PROFILE=SYSTEM
SSLProxyCipherSuite PROFILE=SYSTEM
# 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/pki/tls/certs/localhost.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.)
# ECC keys, when in use, can also be configured in parallel
SSLCertificateKeyFile /etc/pki/tls/private/localhost.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 convenience.
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.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)
#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
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
<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 sent or allowed to be 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 sent 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>
CustomLog "|/usr/sbin/cronolog /var/log/httpd/%Y/%Y-%m-ssl-access_log" combined
#TransferLog "|/usr/sbin/cronolog /var/log/httpd/%Y/%Y-%m-ssl_access_log"
ErrorLog "|/usr/sbin/cronolog /var/log/httpd/%Y/%Y-%m-ssl_error_log"
#Listen 0.0.0.0:443 https
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
DirectoryIndex index.shtml index.html index.htm
DocumentRoot "/home/web/www.reppep.com/"
<Directory "/home/web/www.reppep.com/">
Options All +Indexes -Includes +MultiViews
# AllowOverride None +ExecCGI
</Directory>
AddType text/html .pl
AddType text/html .text
AddHandler markdown .text
Action markdown /cgi-bin/Markdown.cgi
ScriptAlias /cgi-bin/ /home/web/www.reppep.com/cgi-bin/
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Location>
<Location /server-info>
SetHandler server-info
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Location>
RedirectPermanent /chris https://www.reppep.com/~pepper
RedirectPermanent /pepper https://www.reppep.com/~pepper
RedirectPermanent /pepper/album https://www.reppep.com/~pepper/album
RedirectPermanent /pepper/video https://www.reppep.com/~pepper/video
RedirectPermanent /julia/gallery https://www.reppep.com/img/julia/gallery
RedirectPermanent /julia/preblog https://www.reppep.com/img/julia/preblog
Alias /img/julia /img/julia
<Directory /img/julia>
Options All +Indexes +Includes +MultiViews
AuthType Digest
AuthName Julia
AuthUserFile /home/web/htdigest
Require user julia
</Directory>
[root@rocky conf.d]# certbot -d www.reppep.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Certificate not yet due for renewal
You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry.
(ref: /etc/letsencrypt/renewal/www.reppep.com.conf)
What would you like to do?
1: Attempt to reinstall this existing certificate
2: Renew & replace the certificate (may be subject to CA rate limits)
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1
Deploying certificate
Some rewrite rules copied from /etc/httpd/conf.d/www.reppep.com.80.conf were disabled in the vhost for your HTTPS site located at /etc/httpd/conf.d/www.reppep.com.80-le-ssl.conf because they have the potential to create redirection loops.
Successfully deployed certificate for www.reppep.com to /etc/httpd/conf.d/www.reppep.com.80-le-ssl.conf
Added an HTTP->HTTPS rewrite in addition to other RewriteRules; you may wish to check for overall consistency.
Congratulations! You have successfully enabled HTTPS on https://www.reppep.com
If you like Certbot, please consider supporting our work by:
[root@rocky conf.d]# ls
autoindex.conf ssl.conf www.reppep.com.80.conf
DISABLED userdir.conf www.reppep.com.80-le-ssl.conf
README vhost.d
rename.DIS welcome.conf
[root@rocky conf.d]# cat www.reppep.com.80.conf
# This vhost only redirects to HTTPS
<VirtualHost *:80>
ServerName www.reppep.com
ServerAlias www rocky rocky.reppep.com img.reppep.com img.chrispepper.com
UseCanonicalName on
# RedirectPermanent / https://rocky.reppep.com/
# RedirectPermanent / https://www.reppep.com/
CustomLog "|/usr/sbin/cronolog /var/log/httpd/%Y/%Y-%m-www-access_log" combined
RewriteEngine on
RewriteCond %{SERVER_NAME} =img.reppep.com [OR]
RewriteCond %{SERVER_NAME} =img.chrispepper.com [OR]
RewriteCond %{SERVER_NAME} =rocky.reppep.com [OR]
RewriteCond %{SERVER_NAME} =www.reppep.com [OR]
RewriteCond %{SERVER_NAME} =www [OR]
RewriteCond %{SERVER_NAME} =rocky
RewriteRule ^ https://www.reppep.com%{REQUEST_URI} [END,NE,R=permanent]
RewriteCond %{SERVER_NAME} =www [OR]
RewriteCond %{SERVER_NAME} =www.reppep.com [OR]
RewriteCond %{SERVER_NAME} =rocky [OR]
RewriteCond %{SERVER_NAME} =rocky.reppep.com [OR]
RewriteCond %{SERVER_NAME} =img.chrispepper.com [OR]
RewriteCond %{SERVER_NAME} =img.reppep.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
[root@rocky conf.d]# cat www.reppep.com.80-le-ssl.conf
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerName www.reppep.com
ServerAlias www rocky rocky.reppep.com img.reppep.com img.chrispepper.com
UseCanonicalName on
# RedirectPermanent / https://rocky.reppep.com/
# RedirectPermanent / https://www.reppep.com/
CustomLog "|/usr/sbin/cronolog /var/log/httpd/%Y/%Y-%m-www-access_log" combined
RewriteEngine on
# Some rewrite rules in this file were disabled on your HTTPS site,
# because they have the potential to create redirection loops.
# RewriteCond %{SERVER_NAME} =img.reppep.com [OR]
# RewriteCond %{SERVER_NAME} =img.chrispepper.com [OR]
# RewriteCond %{SERVER_NAME} =rocky.reppep.com [OR]
# RewriteCond %{SERVER_NAME} =www.reppep.com [OR]
# RewriteCond %{SERVER_NAME} =www [OR]
# RewriteCond %{SERVER_NAME} =rocky
# RewriteRule ^ https://www.reppep.com%{REQUEST_URI} [END,NE,R=permanent]
SSLCertificateFile /etc/letsencrypt/live/www.reppep.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/www.reppep.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>
</IfModule>
[root@rocky conf.d]# apachectl restart
[root@rocky conf.d]# certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Found the following certs:
Certificate Name: www.reppep.com
Serial Number: 336e65ed14fabc46be8139c22681a100077
Key Type: ECDSA
Domains: www.reppep.com
Expiry Date: 2024-12-13 22:35:58+00:00 (VALID: 50 days)
Certificate Path: /etc/letsencrypt/live/www.reppep.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.reppep.com/privkey.pem
[root@rocky conf.d]# more /etc/letsencrypt/options-ssl-apache.conf
# This file contains important security parameters. If you modify this file
# manually, Certbot will be unable to automatically provide future security
# updates. Instead, Certbot will print and log an error message with a path to
# the up-to-date file that you will need to refer to when manually updating
# this file. Contents are based on https://ssl-config.mozilla.org
SSLEngine on
# Intermediate configuration, tweak to your needs
SSLProtocol all -SSLv2 -SSLv3 -TLSv1 -TLSv1.1
SSLCipherSuite ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA25
6:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20
-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-G
CM-SHA384
SSLHonorCipherOrder off
SSLSessionTickets off
SSLOptions +StrictRequire
# Add vhost name to log entries:
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" vhost_c
ombined
LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common
[root@rocky conf.d]# grep Cert ssl.conf
# Point SSLCertificateFile at a PEM encoded certificate. If
SSLCertificateFile /etc/pki/tls/certs/localhost.crt
SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
# Server Certificate Chain:
# Point SSLCertificateChainFile at a file containing the
# the referenced file can be the same as SSLCertificateFile
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt
# Certificate Authority (CA):
#SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt
# o ExportCertData:
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
[root@rocky conf.d]#