Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

In Production , Rest conectors are failing at SSL handshake



PRPC Rest connectors are failing to connect to the target system using 2-way SSL Handshake.

Error Messages Caught unhandled exception: hostname in certificate didn't match: <hostname1> != <hostname2> OR <hostname3>     at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_d40effb9d40161e004b994e2250c8b2d.step5_circum0(
    at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_d40effb9d40161e004b994e2250c8b2d.perform(
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
    at com.pegarules.generated.activity.ra_action_invoke_b58a312a538cfaba5e4ed8bc3b46c2cf.step7_circum0(

Steps to Reproduce

Not Applicable

Root Cause

The root cause of this problem is defect/misconfiguration in the PRPC operating environment. The endpoint REST service url uses hostname that does not match the identity information in certificates. By default, PRPC performs strict hostname verification.


This issue is resolved by making the following change to the PRPC operating environment: Modify the hostname in URLs or update certificates to match the REST service URL hostname.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us