BKG

hi @DeBaschdi, I did the install the plugin and everything seemed to be going well but when I get to START THE SERVER it jusut not happening. Any clue? Thanks.

Thank you all again.

Just tested with the downloads and it does exactly what I wanted. Thanks @JonathamM

bare with me please... so the end result should be like in the screen shot?

I see. I thought /config/qBittorrent/downloads is the place wher the QB is saving the torrent files and not the actual downloaded content. Forgive my ignorance, my downloading days were long in the past 10 years ago and i now almost start from scratch. Also, i am new to dockers and thought if I specified the path in the container template it would overwrite the rest. So to be clear the current /config/qBittorrent/downloads path must be changed to /mnt/user/MULTIMEDIA/downloads?

Hi wgstarks, i have one more question to ask for the downloaded data. I have modified the path for /mnt/user/appdata/ to a new path on the dedicated share, but the download content still lands in the /mnt/cache/appdata/binhex-qbittorrentvpn/qBittorrent/downloads. Do I have to do anything with the download management in the qbittorrent? Thanks,

!!!it works now with 8088!!! but i did try that earlier by changing the manually in the web browser from 8080-to-8088 and it didn't work. I think I know what was the problem: when I tried originally it did not work even when I manually changed the port 8080-to8088 in the browser after trying the WEBUI. I believe the reason for that was that i was trying the container without the VPN config file being placed into the ovpn folder. Now, it works with the default port 8080 which I just changed in the config. Now, it works with only one network in the LAN_NETWORK 192.168.0.0/24 Verdict - it needs to have a valid ovpn config in order to run. It seems there is no need to change the default port. @binhex, @wgstarks, Thanks for all your patience and help.

@wgstarks I know, that is the problem. No matter what changes I make to the port it sticks with 8080.

tried that too... here is the snap shot.

tried that, no luck...

the IP of the PC is 192.168.20.0/24 network but passed to other subnets in my network setup. For example, i can hit my router on 192.168.0.0/24 network, my cameras on 192.168.10.0/24 network, and my unraid on 192.168.10.0/24.

The other thing is - the port is not changing from 8080 to 8088

container LAN is 192.168.0.0/24. unless i am confusing this question with something else. Thanks,

i presented the PDF as a backup to show that each individual network is working properly with its respective components - VMs, dockers except for the WEBUI for the QB. As a troubleshooting step i downloaded and installed the other QB build which works with the same network parameters, but doesn't have VPN built-in like yours does (see attached). See attached picture. I do believe the problem is in the setup. Can yo please expand on this quote above? Thanks,

No , I don't try and use the VM to connect to QB. I presented the PDF to reflect the high-level picture of what I have and that I can connect to to other docker-containers on the 192.168.0.0/24 network. I do not use the 192.168.10.0/24 network to connect to QB. Again, I have two physical networks right now, one allocated to VM and the other to Docker.