AH02411: SSL Proxy: Peer certificate does not match for hostname

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux (RHEL) 7, 8, 9
    • Apache httpd 2.4.x
  • JBoss Web Server 3.x
  • Red Hat JBoss Core Services (JBCS)
    • Apache httpd 2.4.x
  • mod_proxy
  • mod_cluster

Issue

  • After upgrading to httpd 2.4 from 2.2, we got the following error message in error_log configuring SSL/TLS between httpd and EAP:-
AH02411: SSL Proxy: Peer certificate does not match for hostname 10.0.0.1

Resolution

It is caused by mismatch between hostname/IP address which httpd accesses as a back-end server and subjectAltName entries of type DNSName or CN attributes in a server certificate which EAP provides. You have to recreate EAP's server certificate or set off to SSLProxyCheckPeerName and SSLProxyCheckPeerCN of httpd configuration.

Note that the default value of SSLProxyCheckPeerCN is off in httpd 2.2.x and on in httpd 2.4.x. Note that SSLProxyCheckPeerExpire and SSLProxyCheckPeerName also now default to on in 2.4.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments