Hi,
I am currently setting our up Cloud Connector, but am having issues connecting through to HCP.
I am setting up the connection via our proxy, and have specified port 443 (per request from our infra team). The connection is failing, and I can see the following lines in the logs:
#I/O Exception (Java.Net.socketexception) caught when connecting to the target host: Software caused connection abort: recv failed (local port 62804 to address 0.0.0.0, remote port 443 to address <IP of proxy server>)
Our firewalls have been setup to only allow 443 access - if I try to change the port number to 80 I see in the logs a connection refused error.
I tried connecting through using a test HCC running on my laptop - specifying port 80 for the proxy server worked fine, but specifying 443 failed as well.
Has anyone else specified 443 for the Proxy Port configuration within HCC - or does the HCC -> Proxy configuration need to be on a non-SSL port?
Thanks for your help!
Todd
Hello Todd,
I guess you are mixing here two things:
Typically, proxies are offering only a single port for both plain and encrypted connections. So, if your proxy is listening on port 80, you need to configure port 80 as proxy port in SCC (it's not HCC ...).
The other thing is the port of the target server. For HTTPS many companies, obviously also yours, setup their firewalls/proxies to allow only connections to port 443. This is ok and should not hurt. All HCP endpoints are listening on port 443 for HTTPS.
From your description I get that using proxy port 80 let's you connect successfully so this seems to be the correct configuration. But there might be one more thing needed to be configured, if the SCC is in some special network segment. In such environments also the list of target hosts is often pretty limited. You need to ensure that the hosts mentioned in the Prerequisites network section are not blocked by your firewall, otherwise connectivity will fail.
Best regards,
Markus
Add a comment