I have set-up a bunch of containers on my Pr4100 and I have been trying to put some of those services behind a reverse proxy.
As long as the Nginx proxy manager container references the network of another container, I can build a proxy using that container’s name. I can also use container’s ip.
However, I can am unable to build a proxy using the NAS IP and port where the service runs (despite being able to access that service via my Web browser using NAS_IP:PORT.
I won’t have that problem with other devices. Is there a firewall on the PR4100 that would prevent communication between containers using the Host IP? Nginx is just an example here, I have had the same issue trying to link sonarr and qbittorrent for example.
Have you opened a Support Case? If not opened, for more information, please contact the WD Technical Support team for the best assistance and troubleshooting:
It’s possible that there could be some firewall settings on your PR4100 causing the communication snag between containers using the host IP.One workaround you might consider is trying to tweak the network settings within Docker itself to allow for smoother communication. Another option could be exploring mobile proxies, which might offer a different approach to your networking needs.Ultimately, troubleshooting these kinds of issues can be a bit of trial and error, but with a bit of persistence, you’ll likely find a solution that works for you.
That just added to the list of limitations of a busybox and the pr4100. I moved all the docker stack to a mini pc on Debian. I don’t have a single problem anymore plus started at looking a some more resource intensive things for my homelab.
To set up communication between your Docker containers using Nginx Proxy Manager, you’ll want to ensure that your containers are on the same Docker network. This way, they can talk to each other using their service names as hostnames. For instance, in your nginx.conf file, you could reference the service name directly. Also, if you need more control over your proxies or are working with sticky sessions, check out https://proxyrotator.com/sticky-proxies/sticky-datacenter-proxies/ to get some reliable proxy options.
