nginx-proxy VS docker-swag

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.

https://docs.linuxserver.io/general/swag makes the setup of Authelia very simple.

If you're issuing certs, you might as well centralize with a reverse proxy etc etc. -- take a look at something like a combination of Duckdns and SWAG from linuxserver.io (https://docs.linuxserver.io/general/swag), which does a lot of the heavy lifting for integrations with Lets Encrypt.

Linuxserver.io maintains a reverse proxy (SWAG) and they have a github repo of all the configs they support, nextcloud being one of them (ofc to do it on your own you have to merge a few of the includes they have ssl.conf, proxy.conf, etc).

I have a domain through Cloudflare and I use a Cloudflare tunnel to expose my services on my domain. Geoblocking helps filter a lot of erroneous traffic. Cloudflare also has some useful features to help with blocking malicious attacks and bots. For my reverse proxy, I use SWAG

Long-time amateur here. I tried a bunch of different methods for reverse proxies, and in the end, I used the SWAG docker container from Linuxserver.io, which simplifies it a great deal, and helped me understand the proper syntax.

This is what I used: https://docs.linuxserver.io/general/swag

It's all in their repo https://github.com/linuxserver/docker-swag and docs https://docs.linuxserver.io/general/swag