n00bmaster

The only thing I remember is ... I did manage to resolve with but with a few issues around the web UI and port mapping. Exactly like I talked about on post #3. I had to make sure all of them were privoxying in the same place, using the same VPN. VPN tunnel was strict so had to play around with the VPN_INPUT_PORT and a couple of other parameters. That's all I can say, really. All from memory as it's been a while. Sorry I can't be of more help.

I'm afraid I can't help with this. It's been ages since I've turned on my Unraid server -- anything unnecessary is switched off due to the rising utility costs☹️ So, I can't remember heads or tails with the config.

Yes, all the Docker Apps are in the same subnet. By restrictions, are you referring to the content of my first post? I didn't resolve it exactly but came up with a workaround by slightly changing my setup (as mentioned in post 3). Otherwise, I currently have no restrictions -- the apps are working together as they should -- it's just the little niggles I mentioned earlier (with the WebUI and port mappings) but I probably need to build further understanding of Docker for them.

I definitely need to have a proper read through of the Docker FAQ page -- I'm sorry for my ignorance but just one quick question; so how come I'm able to browse qbittorrent WebUI at 9090 then? Doesn't that mean some part of it has been changed?

I did click the link and generated it the way Squid's post suggested which was to edit the container template and hit "Apply". What I pasted earlier was copied from there.

This is what you meant, right? root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-qbittorrentvpn' --net='br1' --ip='192.168.7.130' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'TCP_PORT_6881'='6881' -e 'UDP_PORT_6881'='6881' -e 'TCP_PORT_8080'='9090' -e 'TCP_PORT_8118'='8118' -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='redacted' -e 'VPN_PASS'='redacted' -e 'VPN_PROV'='redacted' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'WEBUI_PORT'='9090' -e 'LAN_NETWORK'='192.168.7.0/24' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'VPN_INPUT_PORTS'='8080' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' I saw 'TCP_PORT_8080'='9090' ..so I guess it hasn't mapped it like I thought it had To clarify, both of their (qbittorrent and sabnzbd) WebUI work. I can left-click qbittorrent > WebUI and it takes me to it to the correct port (9090). It just doesn't show 9090 under PORT MAPPINGS column. I can go to the sabnzbd WebUI if I go to IP:Port directly but it just doesn't have the WebUI option in the left-click menu.

I haven't done any installation manually. It's only been point-and-click installations, and any config alternation I did were via the GUI template. Having said that, I'm pretty sure what you've quoted is the same as what I've done i.e. in the template, I have Set the WebUI address to to http://[IP]:[PORT:9090]/ Edited the WebUI Host Port to "Host Port:9090", "Default Value:9090" Edited the Container Variable: WEBUI_PORT to "Value:9090", "Default Value:9090"

Thank you for responding. Whilst I'd still like an input from @binhex on how to correctly do this, I've got it working in the interim. So, I changed the Web UI port to 9090 and set the VPN_INPUT_PORTS to 8080 (for sabnzbd Web UI) in binhex-qbittorrentvpn, and routed binhex-sabnzbd through it. As for Sonarr and Radarr, I'm Privoxying them through binhex-qbittorentvpn. Now, they can reach to both binhex-qbittorrentvpn and binhex-sabnzbd from the Download Clients. There are some (minor) issues though; Unraid / Docker / binhex-sabnzbd / Left-click Menu, "Web UI" option no longer shows up. Unraid / Docker / binhex-qbittorrentvpn / PORT MAPPINGS (APP TO HOST), it's still showing IP:8080/TCP <=> IP:8080 (as opposed to 9090 as I have changed it). Except for those, all seem to be working okay.

I apologise if this isn't the right place for this kind of query. I checked the Docker Containers forums but they all seem to be for the application-specific config issues. So I figured I would try this here. I use binhex-sabnzbdvpn with Sonarr/Radarr both privoxying through it. All three of them are working great together. I also have binhex-qbittorrentvpn which has its own IP and is in the same subnet (with the apps mentioned above). However, I cannot get it to be reached by Sonarr/Radarr. In Sonarr/Radarr > Settings > General > Proxy, I have already added binhex-qbittorrentvpn's IP to the "Ignored Addresses". I have also checked "Bypass Proxy for Local Address". And if the VPN is not enabled, binhex-qbittorrentvpn can be reached from Sonarr/Radarr. However, when the VPN is enabled, they just don't see it. I have read binhex's VPN Docker FAQ and understood that due to the iptables tightening, when the VPN is on it might not allow the connections from the outside into the VPN tunnel. So, I had set the WebUI port (8080) in VPN_INPUT_PORTS in the binhex-qbittorrentvpn template but still, no joy. So, I'm stumped. What am I missing here? Any ideas?

This is now resolved. I played around and found a way. I ensured eth1 is up but it doesn't have any IP of its own so that Unraid WebUI isn't available at this subnet. Also, enabled bridging -- eth1 is the only member of br1. SETTINGS / Network Settings / eth1 / IPv4 address assignment: None Then, I configured br1's address range in Docker and defined a DHCP pool separate from that in the router (to avoid the same IP being assigned). SETTINGS / Docker / IPv4 custom network on interface br1: Restarted the services and all working as they should now.

Hello, Hope everyone is keeping well. I am a new Unraid user having just set up my server only a few days ago. Got my Plex migrated, up and running today. I have 2 NIC on my server; one is the built-in NIC on the motherboard and the other is from a PCIe card. I have two subnets at home; LAN1 (main) and LAN2. The firewall rules are simple -- LAN1 can access anything in LAN2 but the reverse is blocked except for established and related. LAN1 is plugged in the built-in NIC and LAN2 in the other one. In SETTINGS / Network Settings / eth0 (LAN1) and eth1 (LAN2) have different subnets and respective gateways. I have also unbonded them. I have given Plex a Fixed IP (Custom : eth1) and it's working fine. The bit that bothers me is when I go to eth1's IP in the browser, it takes me to unraid login page and that...wasn't my intention. I want to be able to reach Unraid only through eth0's address. LAN2 is plugged in solely for Plex. Before Unraid, I used to have a physical box sitting in LAN2 serving Plex and that's what I'm trying to recreate, if that makes sense. What am I doing wrong? Or is this a scenario for which I should have a VM?