rmp5s Posted May 19, 2019 Share Posted May 19, 2019 I have a few Docker containers that I can get into, no problem. Sonarr and Radarr, with "bridge networks"...some 172 IP -> server IP...punch in the IP and port, log in no problem. Even Plex..."host network" with no port mappings. IP and port, log in no problem. But the NZBGet Docker keeps giving me a "refused to connect" error. It's got the same type of setup as Sonarr and Radarr (they're all Binhex containers) with its own unique IP and port. Not sure why I can't get to the webUI. Anyone else have this happen before? Quote Link to comment
[email protected] Posted September 25, 2019 Share Posted September 25, 2019 I'm having the same issue.... Did you ever get this resolved? If so, what was the issue? Quote Link to comment
rmp5s Posted September 26, 2019 Author Share Posted September 26, 2019 On 9/25/2019 at 11:15 AM, [email protected] said: I'm having the same issue.... Did you ever get this resolved? If so, what was the issue? Honestly, I don't remember. Sorry. Quote Link to comment
Arbadacarba Posted September 26, 2019 Share Posted September 26, 2019 (edited) Try clearing your cookies in your browser for the server you are connecting to. I had to clear them for both the ip address and then the name of the server Edited September 27, 2019 by Arbadacarba Quote Link to comment
Recommended Posts
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.