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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
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
The above needs fixing too but we'll get to that later. You have the same domain name listed in two VirtualHosts for the same port. That almost always causes problems.
#
# 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>
Well, you've got a bit of a mess. And, not sure exactly how you got in this state. But, let's try some quick changes first and we'll sort the rest after that.
Notice the cert below with Certificate Name aewa.org has both that name and the www subdomain. This is the cert you should be using below.
Change the directory in both lines from aewa.org-0002 to aewa.org
Leave all the rest alone.
The, reload Apache, restart any browser and check both those domain names. Or, use SSL Labs.
This is NOT the END of it though. We need to review the rest of your Certbot config to ensure a later command will not change those lines to something else.
For now, just report on whether that got those names working and we'll take it from there.
There are a number of things to sort out. In your ssl.conf file you will find these lines:
<VirtualHost _default_:443>
# General setup for the virtual host, inherited from global configuration
#DocumentRoot "/var/www/html"
#ServerName www.example.com:443
Uncomment the ServerName line and replace the name with an invalid name. This ensures you don't have the same domain name in multiple places. Maybe like:
Okay, good. We should delete the below two certificates. If you are using either somewhere in addition to Apache let me know before you delete them. But, your current Apache is not using either one:
After that we should clean up some issues with your yukla config too. Both of those domains names use their own certs. Which is fine. But, you have some overlap in your Apache VirtualHost names and ports. That isn't fine.
To start with that, please show the current output of below. Just want to be sure we are working with the latest info.
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
And one other thing, while upgrading piwigo I encountered this error in the log:
[Wed Jan 28 07:33:12.096769 2026] [ssl:warn] [pid 29443:tid 139863628754624] AH01909: www.aewa.org:443:0 server certificate does NOT include an ID which matches the server name
No, definitely do not delete that (yet). It is used by Apache.
Look back at the certbot certificates list in post #3. The yukla27.org cert has just the www domain name in it. And, the yukla27.org-0001 cert has just yukla27.org domain in it. You then have two separate VirtualHosts for those domains and each uses its matching cert.
That is different than what you had for aewa so yukla need a different sequence of corrections. I'll need some time to devise a plan but wanted to make sure you did not delete that in the meantime.