2460641 - Adding subaccount to SAP Cloud Connector fails due to network issues

Symptom

While adding an SAP BTP subaccount to SAP Cloud Connector, or refreshing the subaccount certificate (regardless to SCC version), one of the following errors gets raised:

417 Could not download configuration file — see ''Logs'' for details

500 Failed to sign the cloud connector certificate for subaccount <subaccount>@<region>. Verify configuration and proxy settings — see ''Log And Trace Files'' for details

Moving on, upon checking SCC trace for details, an error similar to the following one is recorded:

  Preparation of tunnel certificate for <subaccount>@<region> account failed.
      com.sap.scc.servlets.CriticalSccException: Preparation of tunnel certificate for <subaccount>@<region> account failed.
      ...

java.net.ConnectException: Connection timed out

java.net.ConnectException: Connection refused

  java.net.SocketException: Connection reset

java.net.ConnectException: Connection reset by peer.

javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

  Caused by: java.net.UnknownHostException: proxy

Unexpected exception while establishing tunnel connection for tunnel ... UnknownHostException

java.io.IOException: An existing connection was forcibly closed by the remote host

account failed - host proxy not found.

Environment

SAP Cloud Connector release independent;
SAP BTP Cloud Platfom.

Product

SAP Connectivity service 2.0

Keywords

BTP, Business Technology Platform, Subaccount, 500, 417, certificate, HTTPS, proxy, Cloud Connector, IP address, region host, connection timed out, connection refused, connection reset by peer, peer not authenticated, sub-account, subaccount, tunnel, BTP cockpit , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.