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

Unable to connect the service from connect-rest over https



For any Connect-REST rule over HTTPS, No Cert setting is not recognized and test-Connectivity does not function.

The actual REST call is also failing

Error Messages

2017-04-17 15:54:26,695 [http-nio-8080-exec-3] [ STANDARD] [ shared] [ ADW:01.01.01] (ector.Rule_Connect_REST.Action) ERROR RU567817 - Connection reset
2017-04-17 15:54:26,695 [http-nio-8080-exec-3] [ STANDARD] [ shared] [ ADW:01.01.01] ( internal.mgmt.Executable) ERROR RU567817 - Exception Caught unhandled exception: Connection reset
Caused by: Connection reset

Steps to Reproduce

1) Create a Connect-REST.
2) Try to hit any https URL, an error occurs.
3) Create .jks file with .pfx file provided by the end client and use the .jks file as truststore at the REST connect rule.
4) Try to hit the service with SSL settings as suggested by product, observe the error.

Root Cause

A defect or configuration issue in the operating environment.

As per the error there is a connection reset during read socket operation and is not related to SSL/TLS handshake.

Pega 7.2.1 does support REST connect rule level truststore and keystore.

Also the user is having the REST service hosted on a different domain which has some configuration issue preventing the REST service call.


User moved hosted the REST service in the same domain as the PEGA server is hosted and the connection was successful.

Published May 17, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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