January 20, 20251 yr I wanted to make this post before submitting a bug ticket, not knowing whether or not this is expected behavior. I have a container "binhex-nzbhydra2" which I route through a separate VPN enabled container "binhex-sabnzbdvpn". Generally speaking this seems to be working fine and I'm not aware of any issues such as IP leak or connectivity problems. I used the guide created by spaceinvaderone that was linked here to accomplish this: All this said, I have noticed that when I install or update another container unrelated to nzbhydra2, it will inherit the port mappings of that container in the GUI. I believe this may only be a visual error but without 100% certainty, as I'm still able to access the nzbhydra container via the ip and port that are established by sabnzbd. The example below demonstrates the issue, I just updated the tautulli container and the port mappings for nzbhydra2 show the same (usually this field is blank).
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.