# Certificate name mismatch **URL:** \ **Category:** Help\ **Created:** [January 20, 2026, 3:57pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733 "2026-01-20T15:57:45Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 20, 2026, 3:57pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/1 "2026-01-20T15:57:45Z")
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](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. My domain is: **[aewa.org](http://aewa.org)** I ran this command: **[ssllabs.com](http://ssllabs.com) Server Test for [www.aewa.org](http://www.aewa.org) and [aewa.org](http://aewa.org).** It produced this output: **"Certificate name mismatch" for [www.aewa.org](http://www.aewa.org)** My web server is (include version): **Apache/2.4.37 (Rocky Linux)** The operating system my web server runs on is (include version): **Rocky-Linux-8.10** My hosting provider, if applicable, is: **GWS** 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): **certbot 1.22.0** **The [ssllabs.com](http://ssllabs.com) test gave the mismatch error for [www.aewa.org](http://www.aewa.org) but worked without a error for [aewa.org](http://aewa.org).** **Pretty sure this is a config error and I could use an assist in fixing it.** **TIA - Bill (OKC, OK)** ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 20, 2026, 4:41pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/2 "2026-01-20T16:41:50Z")
Let's start with you showing the output of these commands. ```nohighlight sudo certbot certificates sudo httpd -t -D DUMP_VHOSTS ``` You showed the list of certificates in a thread from Aug2025 but you never followed up. We need to see the current list anyway. I am pretty sure Rocky uses `httpd` in that command but just in case you may need to replace `httpd` with `apache2ctl` or even `apachectl` ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 20, 2026, 5:51pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/3 "2026-01-20T17:51:01Z")
Here you go: Found the following certs: ```nohighlight Certificate Name: aewa.org-0001 Serial Number: 63063044aa4ef7a0fad8b57e872789aa81c Key Type: RSA Domains: aewa.org yukla27.org Expiry Date: 2026-04-13 07:14:24+00:00 (VALID: 82 days) Certificate Path: /etc/letsencrypt/live/aewa.org-0001/fullchain.pem Private Key Path: /etc/letsencrypt/live/aewa.org-0001/privkey.pem Certificate Name: aewa.org-0002 Serial Number: 5acbcbb6a6e0beacf443e2fc872bf625aca Key Type: RSA Domains: aewa.org Expiry Date: 2026-04-13 07:14:27+00:00 (VALID: 82 days) Certificate Path: /etc/letsencrypt/live/aewa.org-0002/fullchain.pem Private Key Path: /etc/letsencrypt/live/aewa.org-0002/privkey.pem 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: 81 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: 82 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: 82 days) Certificate Path: /etc/letsencrypt/live/www.yukla27.org/fullchain.pem Private Key Path: /etc/letsencrypt/live/www.yukla27.org/privkey.pem ``` * * * and: VirtualHost configuration: \*:80 is a NameVirtualHost default server [aewa.org](http://aewa.org) (/etc/httpd/conf.d/aewa.org.conf:5) port 80 namevhost [aewa.org](http://aewa.org) (/etc/httpd/conf.d/aewa.org.conf:5) alias [www.aewa.org](http://www.aewa.org) port 80 namevhost [www.yukla27.org](http://www.yukla27.org) (/etc/httpd/conf.d/le-redirect-www.yukla27.org.conf:1) alias [yukla27.org](http://yukla27.org) port 80 namevhost [www.yukla27.org](http://www.yukla27.org) (/etc/httpd/conf.d/yukla27.org.conf:4) \*:443 is a NameVirtualHost default server [aewa.org](http://aewa.org) (/etc/httpd/conf.d/aewa.org-le-ssl.conf:2) port 443 namevhost [aewa.org](http://aewa.org) (/etc/httpd/conf.d/aewa.org-le-ssl.conf:2) alias [www.aewa.org](http://www.aewa.org) port 443 namevhost [www.aewa.org](http://www.aewa.org) (/etc/httpd/conf.d/ssl.conf:40) port 443 namevhost [www.yukla27.org](http://www.yukla27.org) (/etc/httpd/conf.d/yukla27.org-le-ssl.conf:2) port 443 namevhost [www.yukla27.org](http://www.yukla27.org) (/etc/httpd/conf.d/yukla27.org.conf:8) alias [yukla27.org](http://yukla27.org) ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 20, 2026, 5:58pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/4 "2026-01-20T17:58:18Z")
> [@wildbi111](#): > > /etc/httpd/conf.d/ssl.conf > /etc/httpd/conf.d/aewa.org-le-ssl.conf Please show contents of those two files. > [@wildbi111](#): > > port 443 namevhost [www.yukla27.org](http://www.yukla27.org) (/etc/httpd/conf.d/yukla27.org-le-ssl.conf:2) > port 443 namevhost [www.yukla27.org](http://www.yukla27.org) (/etc/httpd/conf.d/yukla27.org.conf:8) > alias [yukla27.org](http://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. ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 20, 2026, 6:51pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/5 "2026-01-20T18:51:35Z")
here's ssl.conf: ```nohighlight # # 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 ## # 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. # #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]+$/ # # 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 SSLOptions +StdEnvVars SSLOptions +StdEnvVars # 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" ``` ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 20, 2026, 6:52pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/6 "2026-01-20T18:52:59Z")
and /etc/httpd/conf.d/aewa.org-le-ssl.conf: ```nohighlight #ServerName www.aewa.org #ServerAlias aewa.org ServerName aewa.org ServerAlias www.aewa.org DocumentRoot /var/www/aewa.org ServerPath /var/www/aewa.org XBitHack on ScriptAlias /cgi-bin/ /var/www/cgi-bin/ #RedirectPermanent /mailman/ https://aewa.org/mailman/ ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ Alias /aewa/ /var/lib/mailman/archives/private/aewa/ Alias /listserv/ /var/www/www allow from all Options +Indexes +Includes +FollowSymLinks +IncludesNoExec AddOutputFilter INCLUDES .cgi Allow from all Options +ExecCGI +Includes AddOutputFilter INCLUDES .cgi AllowOverride Options FileInfo AllowOverride None Options ExecCGI Order allow,deny Allow from all Options MultiViews FollowSymLinks AllowOverride None Order allow,deny Allow from all AddDefaultCharset Off Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/aewa.org-0002/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/aewa.org-0002/privkey.pem ``` ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 20, 2026, 8:54pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/7 "2026-01-20T20:54:14Z")
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. > [@wildbi111](#): > > ```nohighlight > 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: 81 days) > Certificate Path: /etc/letsencrypt/live/aewa.org/fullchain.pem > Private Key Path: /etc/letsencrypt/live/aewa.org/privkey.pem > > ``` To use that cert, you must change this file: ```nohighlight /etc/httpd/conf.d/aewa.org-le-ssl.conf ``` In that file are these two lines ```nohighlight SSLCertificateFile /etc/letsencrypt/live/aewa.org-0002/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/aewa.org-0002/privkey.pem ``` 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. ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 25, 2026, 12:03am UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/8 "2026-01-25T00:03:42Z")
OK, I edited the two lines in /etc/httpd/conf.d/aewa.org-le-ssl.conf and restarted httpd. Do you want me to post the [ssllabs.com](http://ssllabs.com) test results for [aewa.org](http://aewa.org)? Sorry, for the delay, came down with a cold the past two days. ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 27, 2026, 9:16pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/9 "2026-01-27T21:16:44Z")
Mike - You mentioned looking at my certbot config. What should I be looking for? Bill ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 27, 2026, 9:29pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/10 "2026-01-27T21:29:13Z")
Oh, sorry, lost track of your thread. Been busy There are a number of things to sort out. In your `ssl.conf` file you will find these lines: ```nohighlight # 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: ```nohighlight ServerName default.aewa.domain ``` ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 27, 2026, 9:30pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/11 "2026-01-27T21:30:04Z")
After you update that ssl.conf file and reload Apache: Show contents of this file. You can redact the account number if you wish ```nohighlight /etc/letsencrypt/renewal/aewa.org.conf ``` AND, show result of this command: ```nohighlight sudo certbot renew --dry-run --cert-name aewa.org ``` ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 27, 2026, 11:44pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/12 "2026-01-27T23:44:19Z")
Here are the results: ```nohighlight # renew_before_expiry = 30 days version = 5.2.2 archive_dir = /etc/letsencrypt/archive/aewa.org cert = /etc/letsencrypt/live/aewa.org/cert.pem privkey = /etc/letsencrypt/live/aewa.org/privkey.pem chain = /etc/letsencrypt/live/aewa.org/chain.pem fullchain = /etc/letsencrypt/live/aewa.org/fullchain.pem # Options used in the renewal process [renewalparams] account = eb39f92ff8d426fe6eceee440434093b authenticator = apache installer = apache server = https://acme-v02.api.letsencrypt.org/directory key_type = rsa [acme_renewal_info] ari_retry_after = 2026-01-27T10:12:02 ``` The certbot command gave errors: ```nohighlight Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/aewa.org.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Error while running apachectl configtest. AH00526: Syntax error on line 19 of /etc/httpd/conf.d/yukla27.org.conf: SSLCertificateFile: file '/etc/letsencrypt/live/yukla27.org-0001/fullchain.pem' does not exist or is empty Error while running systemctl restart httpd. Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. Failed to renew certificate aewa.org with error: The apache plugin is not working; there may be problems with your existing configuration. The error was: MisconfigurationError('Error while running systemctl restart httpd.\n\nJob for httpd.service failed because the control process exited with error code.\nSee "systemctl status httpd.service" and "journalctl -xe" for details.\n',) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - All simulated renewals failed. The following certificates could not be renewed: /etc/letsencrypt/live/aewa.org/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 renew failure(s), 0 parse failure(s) Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. ``` ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 27, 2026, 11:49pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/13 "2026-01-27T23:49:33Z")
The httpd service was running yesterday but something happened. I'm checking now. ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 27, 2026, 11:59pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/14 "2026-01-27T23:59:54Z")
OK, the server is up and here's the results of certbot cmd: ```nohighlight 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Congratulations, all simulated renewals succeeded: /etc/letsencrypt/live/aewa.org/fullchain.pem (success) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ``` The error was caused by a typo on my part regarding a 2nd web site called [www.yukla27.org](http://www.yukla27.org). ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 28, 2026, 2:49am UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/15 "2026-01-28T02:49:00Z")
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: ```nohighlight sudo certbot delete --cert-name aewa.org-0001 sudo certbot delete --cert-name aewa.org-0002 ``` 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. > [@MikeMcQ](#): > > `sudo httpd -t -D DUMP_VHOSTS` ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 28, 2026, 10:20am UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/16 "2026-01-28T10:20:53Z")
> [@MikeMcQ](#): > > httpd -t -D DUMP\_VHOSTS Here's the output: ```nohighlight 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 ``` ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 28, 2026, 10:31am UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/17 "2026-01-28T10:31:49Z")
I guess you'll need to see this for [yukla72.org](http://yukla72.org). ```nohighlight certbot renew --dry-run --cert-name yukla27.org Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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/www.yukla27.org/fullchain.pem (success) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ``` and this: ```nohighlight cat /etc/letsencrypt/renewal/yukla27.org.conf # renew_before_expiry = 30 days version = 1.22.0 archive_dir = /etc/letsencrypt/archive/www.yukla27.org cert = /etc/letsencrypt/live/www.yukla27.org/cert.pem privkey = /etc/letsencrypt/live/www.yukla27.org/privkey.pem chain = /etc/letsencrypt/live/www.yukla27.org/chain.pem fullchain = /etc/letsencrypt/live/www.yukla27.org/fullchain.pem # Options used in the renewal process [renewalparams] account = eb39f92ff8d426fe6eceee440434093b authenticator = apache installer = apache server = https://acme-v02.api.letsencrypt.org/directory [acme_renewal_info] ari_retry_after = 2026-01-28T05:25:08 ``` There is also a file yukla27.org-0001.conf so here are the results of that. I suspect I should do a certbot delete on it. Do you agree? ```nohighlight cat /etc/letsencrypt/renewal/yukla27.org-0001.conf # renew_before_expiry = 30 days version = 5.2.2 archive_dir = /etc/letsencrypt/archive/yukla27.org-0001 cert = /etc/letsencrypt/live/yukla27.org-0001/cert.pem privkey = /etc/letsencrypt/live/yukla27.org-0001/privkey.pem chain = /etc/letsencrypt/live/yukla27.org-0001/chain.pem fullchain = /etc/letsencrypt/live/yukla27.org-0001/fullchain.pem # Options used in the renewal process [renewalparams] account = eb39f92ff8d426fe6eceee440434093b authenticator = apache installer = apache server = https://acme-v02.api.letsencrypt.org/directory key_type = rsa [acme_renewal_info] ari_retry_after = 2026-01-28T05:25:08 ``` ---
**Author:** ![wildbi111](https://avatars.discourse-cdn.com/v4/letter/w/8dc957/32.png) [@wildbi111](https://community.letsencrypt.org/u/wildbi111)\ **Post date:** [January 28, 2026, 1:37pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/18 "2026-01-28T13:37:53Z")
And one other thing, while upgrading piwigo I encountered this error in the log: ```nohighlight [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 ``` ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 28, 2026, 2:48pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/19 "2026-01-28T14:48:35Z")
> [@wildbi111](#): > > `port 443 namevhost www.aewa.org (/etc/httpd/conf.d/ssl.conf:40)` First, from your latest DUMP\_VHOSTS that domain name still shows in ssl.conf. You should modify that as I described earlier: > [@MikeMcQ](#): > > There are a number of things to sort out. In your `ssl.conf` file you will find these lines: > > ```nohighlight > > > # 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: > > ```nohighlight > ServerName default.aewa.domain > > ``` ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [January 28, 2026, 2:53pm UTC](https://community.letsencrypt.org/t/certificate-name-mismatch/244733/20 "2026-01-28T14:53:00Z")
> [@wildbi111](#): > > There is also a file yukla27.org-0001.conf so here are the results of that. I suspect I should do a certbot delete on it. Do you agree? 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. [Next page](https://community.letsencrypt.org/t/certificate-name-mismatch/244733.md?page=2)