nginx-proxy-automation VS docker-letsencrypt-nginx-proxy-companion

I use this repo as a reverse proxy: https://github.com/evertramos/nginx-proxy-automation/tree/main/docs

https://github.com/evgeniy-khist/letsencrypt-docker-compose https://github.com/evertramos/nginx-proxy-automation

I have this NGINX proxy companion installed on my server, so, in order to have AdGuard as a Docker container I made the following docker-compose.yml working file:

For my nginx proxy using lets encrypt I used this resouce and wordpress was this.

This setup was working until I tried changing from a deprecated Nginx proxy manager to a more up-to-date one, at the same time as setting up Yacht. Subdomains of the working URL also work, no domains/subdomains of the non-working URLs work.

And here you can find various real world examples: https://github.com/evertramos/nginx-proxy-automation#other-projects-using-nginx-proxy

I am using Docker to host Matomo, get Let's Encrypt SSL certificates and run Nginx as a reverse proxy. To make things really easy, we can setup the awesome evertramos/nginx-proxy-automation project. Follow the instructions in the README to setup the containers via Docker. This will automatically create a Docker network called webproxy.

Are you tired of manually setting up SSL certificates for your website? Then you'll love my top repository of the week: Let's Encrypt Companion!

I will also have a look at that, thank you. For the certs I combine the nginx-proxy with a repository called letsencrypt-companion :) That way configuration and SSL is handled automatically!

This setup was working until I tried changing from a deprecated Nginx proxy manager to a more up-to-date one, at the same time as setting up Yacht. Subdomains of the working URL also work, no domains/subdomains of the non-working URLs work.