TLS handshake errors running docker on the Azure

[Kieran260]

Hi, if this isn't the right place for this question please direct me towards somebody who may be able to help!

We're using Azure container apps to host the container as a proxy, pulling it directly from docker hub and have all of the environment variables configured. The three keys are inside of the container and the container is running. We are running the exact same configuration locally and we're able to communicate via HTTPS, even from another machine on the LAN.

Problem: For the cloud hosted container when trying to access the proxy via https we're getting this error: Client sent an HTTP request to an HTTPS server. We've got the ingress set up to accept HTTPs only to port 443.

Is there something we're doing wrong here?
Thanks!

[Daeell]

Hi, I experienced a similar issue, did you solve it?

[Kieran260]

Hi, yes I discovered that the cloud service was terminating the requests at the edge into HTTP regardless of ingress settings so the commands proxy won't accept it.

You could add a reverse proxy e.g. NGINX inside a container to forward a new HTTPs connection internally to the command proxy.

There's possibly other easier ways but this is the most cost efficient for my project.