Have gone through various threads and appear to be hitting a wall here.
I’m coming from a windows environment where I had qbittorrent bound to an OpenVPN network (triggered by Sonarr and Radarr, but that’s another challenge). I’m working through setting up a TS-464.
It appears that QNAP actively kills openVPN instances running inside of containers now, so I’m not sure how to apply the older solutions (I’m also very tech adept, but a total Docker novice).
Does anyone have any suggestions that would get me over this hurdle so I can move onto the next one?
I use a Zorin OS Lite VM on my QNAP with Mullvad and qBitorrent. This allows me to also install other utilities inside the virtual machine that I frequently use, such as ffmpeg, mkvtoolnix, mediainfo, 7z, etc. It also allows me to run scripts against my downloads automatically through the post torrent download script setting in qBitorrent.
It’s a personal preference, but I prefer to have my qnap do nothing but store files. I use virtual machines or containers for everything else. I only use containers if it’s a simple program or task. Anything more complex than that, I prefer to use virtual machines.
The virtual machine that I’m using right now for torrents only has 2 CPU cores and 4 GB of RAM allocated to it. I gave it a 30 GB virtual hard drive. I mount a folder on the qnap as the download folder in the virtual machine. This way the downloads from qBitorrent in the virtual machine automatically go to that folder on the qnap that I mounted in the VM.
At least you don’t need to deal with ARM/aarch based docker images there
Do you have to use OpenVPN? Most decent VPN Providers also do Wireguard.
Also, before I switched to using balenaOS in a VM for all my docker things I didn’t have any VPN “app” running on my QNAP. Just going to guess here but perhaps it is that which is killing your OpenVPN connections within docker containers.
To access the NAS via remote, or when I was running docker game servers on it (valheim etc) for friends to connect in I setup ZeroTier via docker image. They do have their own image although the most lightweight one I’ve came across was zyclonite/zerotier.
There is also Tailscale - I cannot say if its better or not as I don’t have the use case and scaling needs to run something like that.
Instead of messing around with dockers or using a VM and incurring performance penalties and reduced resources, I just went the simple way and installed qBittorrent directly on the NAS. I use a Wireguard profile in qvpn and I bind qBittorrent to the Wireguard interface just I previously did on Windows. It’s been working great so far. With qvpn the NAS also is not required to be behind the VPN unless you want it to.
Did you ever get your situation resolved @SupaDawg
I’ve just bought a TS-464 and coming from Windows where I use qBittorrent with a VPN and seem to be hitting exactly the same brick wall as you. No docker experience and not wanting to damage my Plex install (the only thing I HAVE got working so far)…
Your experience is exactly mine, in fact I could have written your post… LOL
I’ve actually been banging my head against the fall on this one. My VPN provider is one of the ones that isn’t supported directly (Ironsocket), and it can seem to fetch the profiles. I’ve had slightly more luck with my own openvpn file, though I can’t get into the web interface to know it’s working.
Do you bypass VPN for anything? It seems to choke Plex remote connections going through VPN. And just stuff like downloading from steam, I don’t need 50gb going through my VPN.
You can always disconnect VPN but I guess I have 2 distinct needs: one must go through VPN, one I really don’t want going through VPN.
This is actually quite similar to how I had things set up on my windows box. I’m trying to avoid VMs this time around in an effort to keep things as simple to maintain as possible, but it’s definitely my fall back plan.
