Azure Https in a container

Question

Hello I followed this page https://learn.microsoft.com/fr-fr/azure/container-instances/container-instances-container-group-ssl to enable https in a container in azure but this has no effect.
Maybe this is not compatible with our instance which is : https://hasura.io/docs/latest/graphql/core/deployment/deployment-guides/azure-container-instances-postgres.html#

Thank you

Answer 1

@yannick ,

There are many Certificate Authority(CA) companies that provide SSL certs. Some of the most popular ones are Let’s Encrypt Certificate Authority (letsencrypt.org), Digicert, beyondtrust, etc., There are also some free SSL CA certs as well. It depends on which ones you would like to go with.

You won’t immediately get an SSL certificate as soon as you buy it. The Certificate authority will get your credentials, make sure you own the claimed domain and follow any other verification processes before issuing a certificate.

Steps involved typically when one has to get the CA cert and use are clearly documented here how-to-get-an-ssl-certificate-for-my-website

In this context, follow this and in the nginx.conf file change server_name from localhost to the correct server name and set the paths for ssl_certificate and ssl_certificate_key correctly (these files should be obtained from your Certificate Authority.

While this article uses Nginx in the sidecar, you can use another TLS provider such as Caddy.

Answer 2

@yannick ,
You created a self-signed public certificate to authenticate your application, hence you will see this warning. Why can't you get a Certificate Authority (CA)-signed certificate for your app? or you can explore the options to bypass this error - https://www.technipages.com/google-chrome-bypass-your-connection-is-not-private-message

Answer 3

@yannick ,
How and what information are you accessing? What error message are you getting? Did you use a self-signed certificate (not a certificate authority)? If yes, then the browser displays a security warning when connecting to the site over HTTPS. You might need to accept the warning or adjust browser or certificate settings to proceed to the page. This behavior is expected.