paranoia_machinery on Nostr: [@thelinuxcast](https://fosstodon.org/@thelinuxcast) You have to make sure portainer ...
[@thelinuxcast](https://fosstodon.org/@thelinuxcast)
You have to make sure portainer and nginx are on the same docker network, check out Christian lempa's portainer tutorial, basically once you deploy nginx proxy manager you need to shut down portainer and redeploy the portainer container on the nginx proxy manager's docker network. You need to do this with all the web facing containers you want to be able to access from the web. Or else you will get a bad gateway error because they are on a different docker network. It helps to have a database docker network for the backend containers and the web app containers that you want to access on nginx proxy manager's network so you can send traffic to them from the public web through the nginx reverse proxy.
You have to make sure portainer and nginx are on the same docker network, check out Christian lempa's portainer tutorial, basically once you deploy nginx proxy manager you need to shut down portainer and redeploy the portainer container on the nginx proxy manager's docker network. You need to do this with all the web facing containers you want to be able to access from the web. Or else you will get a bad gateway error because they are on a different docker network. It helps to have a database docker network for the backend containers and the web app containers that you want to access on nginx proxy manager's network so you can send traffic to them from the public web through the nginx reverse proxy.