December 10, 20214 yr I'll be the first to admit I don't 100% understand docker container networking, but before a few days ago I had a setup that was working fine since early September. I have nginx proxy manager running on the bridge network, and it seems to be handling requests from the wider internet just fine. If I disable the proxy host for overseerr, then my custom domain returns a "You are logged off" page. When I re-enable it, I get a 502 Bad Gateway page. However, when I am on my internal network (whether its from a VM on the unraid server or another device on the network), I can access overseerr from the same IP address and port that nginx proxy manager is supposed to be accessing. Which leads me to believe the problem is in the network NPM is on (bridge) can't access the network that overseerr is on (bro). But I don't know that would have stopped working. Neither NPM nor overseerr have had an update recently, nor has unraid (I am running 6.10.0-rc2 and have been since within a few days of its release because I am a savage). Host Access to Custom Networks under Settings->Docker is enabled, and has been. Am I thinking about this right? is there something else I should be checking? Does anyone know what I need to do to get this running again?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.