Getting SSL Certification issues from load balancer health monitor

Getting SSL Certification issue from Health monitor check.

Configuration

<LoadBalancer>

<Algorithm>RoundRobin</Algorithm>

<Server name="Server1"/>

<Server name="Server2"/>

<Server name="Server3"/>

<MaxFailures>2</MaxFailures>

<ServerUnhealthyResponse>

<ResponseCode>502</ResponseCode>

<ResponseCode>503</ResponseCode>

</ServerUnhealthyResponse>

</LoadBalancer>

<Path/>

<HealthMonitor>

<IsEnabled>true</IsEnabled>

<IntervalInSec>3</IntervalInSec>

<HTTPMonitor>

<Request>

<ConnectTimeoutInSec>10</ConnectTimeoutInSec> <SocketReadTimeoutInSec>30</SocketReadTimeoutInSec>

<Verb>GET</Verb>

<Path>/health</Path>

</Request>
<SuccessResponse>

<ResponseCode>200</ResponseCode>

</SuccessResponse>

</HTTPMonitor>

</HealthMonitor>

javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching <server nme>

Solved Solved
0 1 934
1 ACCEPTED SOLUTION

Your certificate presented by your backend dont have the actual cname (hostname) in SAN part of the certificate, e.g. you fire to example.com and your cert presenting domain.com

either put correct cname or add SAN extensions for each domain name you fire from Apigee

View solution in original post

1 REPLY 1

Your certificate presented by your backend dont have the actual cname (hostname) in SAN part of the certificate, e.g. you fire to example.com and your cert presenting domain.com

either put correct cname or add SAN extensions for each domain name you fire from Apigee