3192250 - Generic Odata connection couldn’t be established

When validating "Generic OData" connection, error message is raised:

Connection "xxxxx" couldn’t be established.
- Data flows can't be used because of errors in the connection.
- Remote tables can't be used because of errors in the connection.

Data Flows: Cause: Invalid odata connection! Getting odata metadata failed because of Get $metadata response: Timed out waiting for tunnel to open for tunnelId account:///99999999-x999-9x9x-x9x9-x9xxx9999999 Excpetion: org.apache.olingo.odata2.api.ep.EntityProviderException: An exception of type 'XMLStreamException' occurred. Code:1500010

SAP Datasphere

Validate Generic OData connection

OData URL is not public

• The OData service URL needs to be publicly available. This information can be found in SAP Help Portal Page Generic OData
• The ODATA URL that is used should be a valid ODATA service. For example, if this is the ODATA url https://services.odata.org/V2/Northwind/Northwind.svc/ that is accessed through Datasphere then there should be a proper metadata for it. When testing https://services.odata.org/V2/Northwind/Northwind.svc/$metadata in the browser the url should be a valid url and should be able to retrieve the metadata of the ODATA service.
• In the Generic ODATA connection in Datasphere the URL field should be https://services.odata.org/V2/Northwind/Northwind.svc without the $metadata
• Make sure the root certificate of https connection is uploaded under System->Configuration->Setting in the Datasphere tenant. This is documented under Manage Certificates for Connections

dwc, data warehouse cloud , KBA , DS-DI-CON , Connections , Known Error