-
I work on a project configured to only accept HTTPS connections. For local development, we use self-signed certificates and it works. I tried to use nginx-proxy-automation to proxy that project, but I got error 500. I had set What I'm doing when I need to work with this project is to stop nginx-proxy-automation and publish the port 443:443 to the project container. However, this prevents me from using nginx-proxy-automation which I have been using to work with multiple projects under distinct local domains (i.e, app.test, app2.test, app3.test, and so on). |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hi! In fact you don´t need any of that... You just add the tls file to the location where is should be, under the domain name, and start the container with TLS activated. It will work it out just fine. I will send a clear example here later, with CloudFlare TLS. |
Beta Was this translation helpful? Give feedback.
-
Just to update, here is how I solved the problem: docker container cp <container_name>:/etc/ssl/private/my.key data/certs/mydomain.test.key
docker container cp <container_name>:/etc/ssl/certs/my.crt data/certs/mydomain.test.crt Where I just copied the certificates from inside the container (which generated them upon build) to the path where the NGINX proxy stores the certificates. |
Beta Was this translation helpful? Give feedback.
Just to update, here is how I solved the problem:
Where
my.key
andmy.crt
are the certificate files in the container andmydomain.test
is the local domain.I just copied the certificates from inside the container (which generated them upon build) to the path where the NGINX proxy stores the certificates.