nginx-proxy VS acme-companion

setting up letsencrypt with nginx-proxy and acme-companion

Here is the link, sorry😅

Shit... Here is the link: https://github.com/nginx-proxy/nginx-proxy

I use the nginx-proxy image and it's acme companion image for automated reverse proxy configuration and certbot.

I'm experiencing a weird situation, and am not sure how to go about finding a solution. I am running the nginx-proxy container (https://github.com/nginx-proxy/nginx-proxy) together with the acme-companion container (https://github.com/nginx-proxy/acme-companion) to provide https connections to all my different applications under different subdomains on the same host (currently, for testing purposes: only two other nginx containers with a plain html page).

https://github.com/nginx-proxy/nginx-proxy for reverse proxy

I currently use this (https://github.com/nginx-proxy/nginx-proxy) and I was able to configure anything via env vars. Some minor nginx include files were needed tho. But no UI. So far I was stunned that it works so well. Deploy a new container add 2 env vars. Done. With automated SSL.

We use the nginx-proxy docker image with its acme-companion to have an auto configuring SSL reverse proxy, so it's really easy to deploy images (we do it based on a merge PR into protected release branches).

We use Traefik for Configuration Discovery in Docker Swarm (add a label with the sub-domain to the service and it will automatically be routed to), for simple setup I always found nginx-proxy to be easy to use with containers.

setting up letsencrypt with nginx-proxy and acme-companion

I'm experiencing a weird situation, and am not sure how to go about finding a solution. I am running the nginx-proxy container (https://github.com/nginx-proxy/nginx-proxy) together with the acme-companion container (https://github.com/nginx-proxy/acme-companion) to provide https connections to all my different applications under different subdomains on the same host (currently, for testing purposes: only two other nginx containers with a plain html page).

We use the nginx-proxy docker image with its acme-companion to have an auto configuring SSL reverse proxy, so it's really easy to deploy images (we do it based on a merge PR into protected release branches).

Just use nginx-proxy and the LetsEncrypt companion as reverse proxy to handle TLS/SSL in front of your web server.

You can simply use this proxy container which automatically generates nginx config based on envs set in your containers. There is also a companion container which takes care of your certs. https://github.com/nginx-proxy/nginx-proxy https://github.com/nginx-proxy/acme-companion

https://github.com/nginx-proxy/acme-companion https://github.com/nginx-proxy/docker-gen https://github.com/projectdiscovery/dnsx https://github.com/projectdiscovery/httpx https://github.com/projectdiscovery/mapcidr https://github.com/debauchee/barrier https://github.com/stedolan/jq https://github.com/ddosify/ddosify https://github.com/kubernetes-sigs/kind https://github.com/mailcow/mailcow-dockerized https://github.com/motiv-labs/janus

If you use Docker anyway, have a look at nginx-proxy and it's acme companion. When running on the same host, it will automatically find other containers via docker.sock and then route and create Let's Encrypt certificates for the (sub-)domain you add via env.

For the signal proxy, they are using nginx and letsencrypt already and the ports 80 and 443. My current setup already involves an nginx proxy as well as a certbot, so how can I host this signal proxy in my infrastructure?

Then to make deployment super easy we're using nginx-proxy which uses docker-gen (and the acme-companion for automatic SSL cert generation) to automatically re-configure an nginx reverse proxy to point to your containers.

I rent a vps and use it to self host various applications. I would now also like to use this as a vpn (similar to a proxy) to safely browse the internet in open wifi etc. I use docker for all apps so far, nginx-proxy as a reverse proxy and acme-companion for HTTPs certificates.