Connection to Public Host could not be established

Products

• CA Process Automation Base

Issue/Introduction

The following error appears in the UI when trying to install a second domain PAM Orchestrator. 

Connection to Public Host could not be established

This occurs after setting the Load Balancer Public Host Name.

Node 1 is working OK via SSL (Previously configured with non-SSL)

Environment

PAM 4.4 GA and later (2 or more PAM Domain Orchestrators)

Load Balancer (F5/Nginx)

Cause

The second node is trying to communicate via SSL internal jetty port (443) but the node 1 is configured with non-SSL (80) port in the PAM\wildfly\standalone\.config\OasisConfig.properties. This occurs because the node 1 was previously configured with non-SSL port.

Resolution

In Node 1:

1. Go to PAM\wildfly\standalone\.config\OasisConfig.properties

2. Search for node.commsv2.port 

3. Change the value set to node.commsv2.port from 80 to 443.

4. Restart PAM Services 

In Node 2:

5. Re-run the installer 

6. Configure the LB URL in Public Host Name and ensure the Public Host Secure Port is set to 443

6. Click on Next. Now it should be able to progress through the Wizard.