Info below. This problem occurred spontaneously (i.e., I caused it at some unknown point). The hostname (which I assume wouldn’t be exposed to the world) is “frodo” and Chrome reports that certificate is issued to “frodo” and issued by “frodo” and /var/log/httpd/ssl_error has errors like: “ssl:warn] [pid 22036] AH01909: RSA certificate configured for does NOT include an ID which matches the server name”

I guess certbot is picking up the hostname – probably because of something dumb I did – but I have no idea how this occurred or how to fix it. It’s curious, this cert covers,, and and both of the dev sites work fine.

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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: It produced this output: The problem occurred at some unknown point. I did force a renwal and that didn’t change anything:

certbot --force-renewal renew

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/

Plugins selected: Authenticator apache, Installer apache
Starting new HTTPS connection (1):
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for
http-01 challenge for
http-01 challenge for
http-01 challenge for
Waiting for verification…
Cleaning up challenges

new certificate deployed with reload of apache server; fullchain is

Congratulations, all renewals succeeded. The following certs have been renewed:
/etc/letsencrypt/live/ (success)

My web server is (include version): Apache 2.4.6

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

My hosting provider, if applicable, is: CentOS 7.6.1810

Yes, I can login to a root shell

No, I’m NOT using cpanel/WHM/etc.

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.35.1

What’s this show:

apachectl -t -D DUMP_VHOSTS

You might have multiple virtual hosts that match, and the one that’s actually in effect may have the old/default certificate.


Hi @novice

there are some certificates -

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2019-07-15 2019-10-13,,,
4 entries duplicate nr. 1
Let's Encrypt Authority X3 2019-06-01 2019-08-30,,,
4 entries
Let's Encrypt Authority X3 2019-04-02 2019-07-01,,,
4 entries

But you don't use one of these, instead there is a self signed certificate:

E=root@frodo, CN=frodo, OU=SomeOrganizationalUnit, 
O=SomeOrganization, L=SomeCity, S=SomeState, C=--
expires in 79 days	

Did you restart your server?

What says

apachectl -S
1 Like

[root@frodo certs]# apachectl -t -D DUMP_VHOSTS
Passing arguments to httpd using apachectl is no longer supported.
You can only start/stop/restart httpd using this script.
If you want to pass extra arguments to httpd, edit the
/etc/sysconfig/httpd config file.

I see that's an error, but I don't know how to solve it. Here's how I would examine the vhosts:

[root@frodo certs]# ls -l /etc/httpd/sites-available/
total 24
-rw-r--r--. 1 root root 391 Oct 2 2018
-rw-r--r--. 1 root root 554 Oct 2 2018
-rw-r--r--. 1 root root 391 Oct 2 2018
-rw-r--r--. 1 root root 554 Oct 2 2018
-rw-r--r--. 1 root root 659 Jul 15 16:17
-rw-r--r--. 1 root root 764 Oct 2 2018

Sorry, didn’t realize you are on CentOS:

httpd -t -D DUMP_VHOSTS
1 Like

Yes, I don’t know how/why I have a self-signed cert or how it’s being served. I guess the CN=frodo is the problem. I don’t know where that is set and I’m pretty certain that only certbot has modified the SSL files since I set up Let’s Encrypt.

Yes, I restarted the server before posting. Sorry not to mention that.

apachectl -S produces no output (just returns the prompt).

That happens if you have multiple vHosts with the same ServerName / ServerAlias.

So the wrong vHost (or the default vHost with a self signed certificate) is used.

apachectl -S should show your vHost configuration.

Are the sites in /sites-available/ are enabled? (in /sites-enabled/ as symlinks)? Perhaps no site is enabled -> the standard vHost is used.

On recent Fedora/CentOS, you need to call httpd, not apache2.


Thanks, yep, some of these details I don't know

1 Like

Below is the vhosts info. Is this ok?

[root@frodo letsencrypt]# httpd -S
VirtualHost configuration:
*:80 is a NameVirtualHost
default server (/etc/httpd/sites-enabled/
port 80 namevhost (/etc/httpd/sites-enabled/
port 80 namevhost (/etc/httpd/sites-enabled/
port 80 namevhost (/etc/httpd/sites-enabled/
*:443 is a NameVirtualHost
default server (/etc/httpd/conf.d/ssl.conf:56)
port 443 namevhost (/etc/httpd/conf.d/ssl.conf:56)
port 443 namevhost (/etc/httpd/sites-available/
port 443 namevhost (/etc/httpd/sites-available/
port 443 namevhost (/etc/httpd/sites-available/
ServerRoot: “/etc/httpd”
Main DocumentRoot: “/var/www/html”
Main ErrorLog: “/etc/httpd/logs/error_log”
Mutex authdigest-client: using_defaults
Mutex ssl-stapling: using_defaults
Mutex proxy: using_defaults
Mutex authn-socache: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/run/httpd/" mechanism=default
Mutex mpm-accept: using_defaults
Mutex authdigest-opaque: using_defaults
Mutex proxy-balancer-shm: using_defaults
Mutex rewrite-map: using_defaults
PidFile: “/run/httpd/”
User: name=“apache” id=48
Group: name=“apache” id=48


is a duplicate. Merge these two definitions to one definition, remove the other version (or change the ServerName to a not existing domain name, so you can reuse it).

One vHost per port with the non-www as ServerName and the www as ServerAlias (or changed).

1 Like

Bingo! That file is the default version, so I’m not sure why it’s matching now, but didn’t previously. It had no ServerName. I uncommented the default ( and restarted httpd and now everything works.

Many thanks!


Yep, now my browser is happy. :+1:

1 Like

Default behavior in some versions of CentOS use the default HTTPS server vs. the explicitly-configured depending on whether or not the file that defines the explicitly-configured HTTPS service comes alphabetically before or after ssl.conf (!!). I remember that @joohoi had come up with a fix for this issue some months ago, but I can no longer remember the status of that fix or which versions of Certbot (and CentOS) would be affected.

This can sometimes explain very confusing behavior where some virtual hosts seem to work and others don’t, or where renaming a virtual host or reorganizing the configuration can change whether or not a site appears to work properly.

1 Like

The underlying issue here is that the LoadModule ssl_module exists only in the ssl.conf per default, so every <IfModule ssl_module> coming before that when parsing the configuration files in alphabetical order get ignored.

The fix, that should already be in version 0.35.1 that @novice is running is adding LoadModule ssl_module to the main httpd.conf before the inclusion of separate VirtualHost config files. I don’t know why this didn’t work here…

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.