ufish205

Adding a screenshot for some clarification: (while on Wireguard tunnel) UNRAID dashboard responds at 192.168.50.161/login (while on Wireguard tunnel) jellyfin responds at 192.168.50.161:8096 (while on Wireguard tunnel) qbittorrent does NOT respond on 192.168.50.161:8080 This shows the NAT translation is working automagically when I connect as the Wireguard peer. Furthermore, the Wireguard VPN running is assigning IPs 10.253.0.1/24, so the dashboard is also available at 10.253.0.1/login, jellyfin is available at 10.253.0.1 port 8096, but qbittorrent is NOT available at 10.253.0.1 port 8080. So either it's not doing NAT because it doesnt know qBittorrent is there, or its the networking mode, or it could even be a different with the docker image, I suppose...

My situation is this: connecting to my home network remotely via Wireguard. I have access to the main UNRAID dashboard. I have two docker containers running, bbergle-jellyfin in host mode and binhex-qbittorrentvpn in bridge mode. I can access my Jellyfin GUI, but I am unable to access my qBitttorrent GUI. I assume this is because of the differences between host and bridge networking modes. HOWEVER, I know that running containers in bridge networking mode is best practices from a security standpoint. Is there a way to make both containers run in bridge networking mode, and still have access to their web GUIs when VPN'd in from an external machine? Or do I have to suck up the security implications, and run them both as host mode for any chance of this working? Thanks!