API Gateway HTTPS not working when calling an API (Transport protocol not supported)

, ,
1

Hello,

using the API Gateway 10.7 docker image, we get an error when calling an API over HTTPS:

image
image882×25 2.05 KB

  • We didn’t change the default configuration of the keystore or truststore
  • An HTTPS port is also configured
  • The native API does support HTTPS
  • A HTTP request over the API Gateway endpoint works
  • No other policies are configured for the API except the standard ones (Transport and Routing)

We can call the native API over HTTPS just fine, but when setting the API Gateway endpoint and the Transport to HTTPS we get the error calling the API Gateway endpoint of the API. We also tested it with other APIs with the same result.

Any help is appreciated!

Best regards

Tristan

2

Hi Tristan,
Is the inbound HTTPs as well? If so can you please check if the https port is exposed in your docker container.

Also, can you try simple petstore API, by default Petstore native API uses HTTPS.

Regards.

1 Like
3

The HTTPS port was missing in the docker compose file and thus not exposed.

Thank you!

Best regards Tristan

1 Like
4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.