cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect new CF accounts to cloud connector

bartdp
Explorer

Hi

We are trying to complete https://developers.sap.com/mission.mobile-dev-kit-level-up.html with a real service, so we try to connect a new SCP CF (AWS Frankfurt) account to our cloud connector. That fails with "417 Could not download configuration file."

When we try to do that with an existing account on CF, it succeeds.

We see a difference in the CF accounts, one seems to be in Rot (old one) and the other in Frankfurt.

Any pointers?

Kind regards

Bart

View Entire Topic
0 Kudos

Hi Viktor,

I am also facing similar issue while connecting cloud connector to Europe(Frankfurt)- AWS region. I am using the Long ID as suggested by you. below are the logs

2020-04-22 06:53:32,110 +0000#WARN#com.sap.scc.config#http-bio-8443-exec-9# #Creating an sslContextProvider for account <account id>@cf.eu10.hana.ondemand.com without SSLContext. Keystore did not contain a certificate.| 2020-04-22 06:53:32,115 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Will retrieve Connectivity CA certificate from SAP Cloud Platform| 2020-04-22 06:53:32,115 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Executing Http Get request to https://connectivitycertsigning.cf.eu10.hana.ondemand.com:443/certificate/management/v1/trusted/ca/a... Id>| 2020-04-22 06:53:32,837 +0000#INFO#com.sap.scc.security#http-bio-8443-exec-9# #Returned Http Response with code 500| 2020-04-22 06:53:32,838 +0000#INFO#com.sap.scc.config#http-bio-8443-exec-9# #Stopping service channels on <account Id>@cf.eu10.hana.ondemand.com| 2020-04-22 06:53:32,838 +0000#WARN#com.sap.scc.rt#http-bio-8443-exec-9# #Tunnel account:///<account Id> is inoperative. SccEndpoint com.sap.scc.config.TunnelSccEndpoint@384c9f4f ok, and context == null| 2020-04-22 06:53:32,840 +0000#ERROR#com.sap.scc.ui#http-bio-8443-exec-9# #SCC handshake failed: 500 — Internal Server Error