Once you complete the change I described to your default VirtualHost in ssl.conf that warning message will change. It will be more obvious that you can ignore it.
The warning is because that default VHost uses a self-signed cert and the domain name in it does not match the ServerName. It still won't after you make the change I described. And that is fine. The message just won't look like something is wrong with your actual aewa VirtualHost and certs.
I think what you are saying is in the ssl.conf I need to add an entry to the
section that says ServerName yukla27.org:443
Is that right?
No, maybe I misunderstand what you mean but I didn't see a line like that in your ssl.conf file that you showed in post #5
Have you changed that file since then? If so, please show it again.
If not, just carefully re-read my post #10 that, in summary, says to change this line in ssl.conf
#ServerName www.example.com:443
to exactly this (note no longer commented out)
ServerName default.aewa.domain
Do Not use a valid ServerName in that ssl.conf default VirtualHost. You can only properly use a domain name in one VHost for a specific port. Using a valid name in that default VHost creates a duplicate. Sadly, Apache does not warn about this except that it won't always produce the correct results.
You don't normally specify a port with ServerName (anywhere) but that isn't the essential bit here.
Is this what you wanted to see?
certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
Certificate Name: aewa.org
Serial Number: 6c7ab8d38c49f537de8286c7f3e481d3fc7
Key Type: RSA
Domains: aewa.org www.aewa.org
Expiry Date: 2026-04-12 09:15:13+00:00 (VALID: 73 days)
Certificate Path: /etc/letsencrypt/live/aewa.org/fullchain.pem
Private Key Path: /etc/letsencrypt/live/aewa.org/privkey.pem
Certificate Name: yukla27.org-0001
Serial Number: 67eda77a298ef9858f8d3eddfd8c3164e45
Key Type: RSA
Domains: yukla27.org
Expiry Date: 2026-04-13 02:16:45+00:00 (VALID: 74 days)
Certificate Path: /etc/letsencrypt/live/yukla27.org-0001/fullchain.pem
Private Key Path: /etc/letsencrypt/live/yukla27.org-0001/privkey.pem
Certificate Name: yukla27.org
Serial Number: 5723604f86444e5a7202f70a136f2599d26
Key Type: RSA
Domains: www.yukla27.org
Expiry Date: 2026-04-13 07:14:38+00:00 (VALID: 74 days)
Certificate Path: /etc/letsencrypt/live/www.yukla27.org/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.yukla27.org/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
root@aewa /etc/letsencrypt/renewal # httpd -t -D DUMP_VHOSTS
VirtualHost configuration:
*:80 is a NameVirtualHost
default server aewa.org (/etc/httpd/conf.d/aewa.org.conf:5)
port 80 namevhost aewa.org (/etc/httpd/conf.d/aewa.org.conf:5)
alias www.aewa.org
port 80 namevhost www.yukla27.org (/etc/httpd/conf.d/le-redirect-www.yukla27.org.conf:1)
alias yukla27.org
port 80 namevhost www.yukla27.org (/etc/httpd/conf.d/yukla27.org.conf:4)
*:443 is a NameVirtualHost
default server aewa.org (/etc/httpd/conf.d/aewa.org-le-ssl.conf:2)
port 443 namevhost aewa.org (/etc/httpd/conf.d/aewa.org-le-ssl.conf:2)
alias www.aewa.org
port 443 namevhost www.aewa.org (/etc/httpd/conf.d/ssl.conf:40)
port 443 namevhost www.yukla27.org (/etc/httpd/conf.d/yukla27.org-le-ssl.conf:2)
port 443 namevhost www.yukla27.org (/etc/httpd/conf.d/yukla27.org.conf:8)
alias yukla27.org
Please show ssl.conf again. Line #40 should not be using www.aewa.org. You already use that domain as a ServerAlias in the VirtualHost in this file /etc/httpd/conf.d/aewa.org-le-ssl.conf and it is working correctly. You can't have the same domain using the same port twice.
Line 40:
<VirtualHost _default_:443>
Please show the entire contents of ssl.conf. Have you changed that commented out ServerName line as I described?
Yes, I made the change ssl.conf to read
Here's the contents of 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
ServerName default.aewa.domain
# 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>
That looks good. It is strange the DUMP_VHOSTS output still showed www.aewa.org in your ssl.conf. You are using a very old version of Apache so maybe that is affecting it. In any case, that default VHost now won't be able to cause confusion with Certbot at least.
Let's see if we can cleanup yukla27. Please show the contents of these two files. There is a duplication of name and port here too.
/etc/httpd/conf.d/yukla27.org-le-ssl.conf
/etc/httpd/conf.d/yukla27.org.conf
Here they are:
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerName www.yukla27.org
DocumentRoot /var/www/yukla27.org
<Directory "/var/www/yukla27.org">
allow from all
Options +Indexes
</Directory>
SSLCertificateFile /etc/letsencrypt/live/www.yukla27.org/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/www.yukla27.org/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>
</IfModule>
#
# Yukla27.org
#
<VirtualHost *:80>
ServerName www.yukla27.org
Redirect / https://www.yukla27.org
</VirtualHost>
<VirtualHost _default_:443>
ServerName www.yukla27.org
ServerAlias yukla27.org
DocumentRoot /var/www/yukla27.org
<Directory "/var/www/yukla27.com">
Options +Indexes
</Directory>
RewriteEngine on
RewriteCond %{SERVER_NAME} =www.yukla27.org
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/yukla27.org-0001/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/yukla27.org-0001/privkey.pem
</VirtualHost>
and
Okay, we can remove a number of problems just by modifying yukla27.org.conf
That config file has a VHost for port 80 with a redirect with a faulty format. It would not work so is a good thing it is not being selected by Apache with the current layout.
It also has a VHost for port 443 that duplicates an earlier VHost. And, its redirect is also incorrect. It would cause a loop if it was activated because it would redirect an HTTPS request to itself.
To fix all of that change yukla27.org.conf to look like below. In its entirety. Nothing more nothing less. There are actually several changes to the VHost for port 443 so be careful when making the change.
The end result is that this VHost for yukla27.org will be the same as for www.yukla27.org except they each use their own cert file.
<VirtualHost *:443>
ServerName yukla27.org
DocumentRoot /var/www/yukla27.org
<Directory "/var/www/yukla27.com">
allow from all
Options +Indexes
</Directory>
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/yukla27.org-0001/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/yukla27.org-0001/privkey.pem
</VirtualHost>
Ok here's what it looks like now, I commented out several lines.
#
# Yukla27.org
#
#<VirtualHost *:80>
# ServerName www.yukla27.org
# Redirect / https://www.yukla27.org
#</VirtualHost>
<VirtualHost _default_:443>
ServerName yukla27.org
# ServerAlias yukla27.org
DocumentRoot /var/www/yukla27.org
<Directory "/var/www/yukla27.com">
allow from all
Options +Indexes
</Directory>
# RewriteEngine on
# RewriteCond %{SERVER_NAME} =www.yukla27.org
# RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/yukla27.org-0001/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/yukla27.org-0001/privkey.pem
</VirtualHost>
Okay, that was one way to go 
All HTTP and HTTPS requests look good for all your domain names - aewa and yukla27 both the bare domain and the www domain.
The HTTP requests get redirected to HTTPS as is recommended. The HTTPS requests all use a certificate with the proper domain name. This is all good.
There is a further refinement to combine the two VirtualHost for yukla27 and www.yukla27 into one. But, I don't see a strong need to do that.
Currently they are in separate VHosts with separate certs. There is nothing technically wrong with that. And, given how simple the VHost configs are that doesn't seem like an admin burden. The effort to combine them would produce little to no added value.
Before concluding though we should check that the auto-renew would work for all of them. Please show output of this. Note the --dry-run will not disturb your existing production certs. It is just a test
sudo certbot renew --dry-run
certbot renew --dry-run
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/aewa.org.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Simulating renewal of an existing certificate for aewa.org and www.aewa.org
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/yukla27.org-0001.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Simulating renewal of an existing certificate for yukla27.org
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/yukla27.org.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Simulating renewal of an existing certificate for www.yukla27.org
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Congratulations, all simulated renewals succeeded:
/etc/letsencrypt/live/aewa.org/fullchain.pem (success)
/etc/letsencrypt/live/yukla27.org-0001/fullchain.pem (success)
/etc/letsencrypt/live/www.yukla27.org/fullchain.pem (success)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Terrific. That's a wrap
Hey thanks a lot! I appreciate your help very much.