nginxconfig.io VS acme-companion

It'd be weird to exclude any repositories, even the sponsors' ones. Like, sure, it's an ad for them (so is wearing a t-shirt with their logo), but at the same time, they maintain some cool projects, like digitalocean/nginxconfig.io. It'd be a shame if people who genuinely want to improve this tool wouldn't get rewarded for that, only because it's DigitalOcean's.

If you wish to do it yourself then take a deep breath, accept the fact it's going to take a while and get grinding! The most frustrating part for me was Nginx. For that, I would recommend DigitalOcean's Nginx configuration tool - https://github.com/digitalocean/nginxconfig.io . Rather than signing up to a paid VPS straightaway, consider something like virtualbox or vmware( free version ) to get a linux distro installed and running and go from there.

Maybe this fits your needs better: https://github.com/digitalocean/nginxconfig.io

You're spot on about the limitations with that nginx proxy manager. Once people get to the point of fine-tuning their Nginx config, a tool like nginxconfig.io becomes really handy. It was originally developed by Digital Ocean, who still hosts an online version of the tool at the URL in its name. Even better, they've open sourced the entire tool so it can be self-hosted.

My hunch is that because I decided to include the acme-companion image in this nginx setup, that maybe it has something to do with the SSL certs? The only other thing I could think of is that I had to combine the networks in order for nginx-proxy and Sonarr both to be able to see my transmission instance via:

Probably want acme with nginx https://github.com/nginx-proxy/acme-companion

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).

Use a reverse proxy to handle TLS/SSL encryption. I find nginx-proxy with companion easy to use, just follow steps 1, 2, 3.

Where I'm running into issues is with the two stacks I have deployed - one is a wordpress stack which uses the wordpress image along with a db image (going by the docs here), and the other is the nginx-proxy and acme-companion (going by the docs here).

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