Sturm

So it turns out that my issue yesterday was, in fact my VPN provider temporarily suspending my account for "unusually high data usage." I must have busted through their unlisted 3TB soft data cap.

Nope. Just went through the procedure to change the password, made sure to use the same password in both my Windows client and the qbvpn container. Windows client works; qbvpn container doesn't. Same messages.

Yes, an asterisk is in the password. But this has been working fine for a month or two (since I started service with TunnelBear) with no problems until the last 24 hours or so.

Hullo, I am back. I have a new problem now that makes no sense to me. Without any changes whatsoever on my part, the VPN portion is giving me `AUTH_FAILED` messages. I'm attaching the relevant excerpt from the `supervisord.log` file. When the container is started with `VPN_ENABLED=no`, it works fine, indicating that the problem is with my VPN credentials. I use TunnelBear for my VPN and my credentials work just fine on their web site as well as when I run their Windows client. So why the credentials suddenly stopped working on this container is beyond me. I've also downloaded the latest OpenVPN files from them just to make sure they are up-to-date with the same result. Any ideas? excerpt.log

Egg on my face. I forgot to copy over all of the necessary OpenVPN files to the config/openvpn/ folder. Thank you for teaching me the `docker logs` command so I could finally see what was causing that exit code. That was entirely my fault and I apologize for taking up your time with my incompetence.

Certainly. Here's the `qbmusic` container: qbmusic: image: binhex/arch-qbittorrentvpn:4.1.9-1-01 container_name: qbmusic network_mode: "containernet" privileged: true environment: - VPN_ENABLED=yes - VPN_USER=<SAME AS ABOVE> - VPN_PASS=<SAME AS ABOVE> - VPN_PROV=custom - LAN_NETWORK=192.168.100.0/24, 172.18.0.0/16 - DEBUG=false - WEBUI_PORT=8091 - UMASK=002 - PUID=1048 - PGID=65540 volumes: - /volume2/media/dockervolumes/qbmusic/config:/config - /volume2/media/downloads/music:/data ports: - "6883:6883" - "6883:6883/udp" - "8091:8091" - "8121:8121"

I am attempting to create two containers from this image, (see the reason why on an rTorrentVPN thread), but this seems impossible. No matter what I set the ports to on a container, there are some hard-coded ports that cannot be changed, and it appears as though that's causing conflicts when I attempt to spin up a second container from the same image. Here's the first container's config in docker-compose.yml (note the custom port numbers): qbittorrentvpn: image: binhex/arch-qbittorrentvpn:4.1.9-1-01 container_name: qbittorrent-vpn network_mode: "containernet" privileged: true environment: - VPN_ENABLED=yes - VPN_USER=<NOT SHOWING> - VPN_PASS=<NOT SHOWING> - VPN_PROV=custom - LAN_NETWORK=192.168.100.0/24, 172.18.0.0/16 - DEBUG=false - WEBUI_PORT=8090 - UMASK=002 - PUID=1048 - PGID=65540 volumes: - /volume2/media/dockervolumes/qbittorrent/config:/config - /volume2/media:/data ports: - "6882:6882" - "6882:6882/udp" - "8090:8090" - "8118:8118" Yet when I create the container, check out the ports that it uses in the attached image. (I highlighted them.) You can also see in that image that the second container did not spin up; it exited with a code of "1". Are these "hard-coded" ports the culprit of causing the second container to fail to load? Whether or not #1 is true, what can I do about this?

Hey, thanks for being patient with me, Cat_Seeder. Okay, so this is exactly the problem I'm running into with qBittorrent. If I'm going to have the same issue with ruTorrent, then perhaps I shouldn't really even bother moving to rTorrent. qBittorrent works fine with my automated workflows from Radarr and Sonarr; it's just when adding/managing torrents manually that I run into the WebUI slowdown. I don't suppose you could share some of your automated workflows through the CLI that I could adapt for qBittorrent? I'm fairly comfortable with bash/zsh. Or at least just point me in some good directions for how to manage torrents manually without the WebUI? That's pretty much correct. As I said, it the actual backend torrenting appears to be running okay, it's just the WebUI that's super-sluggish and 90% non-responsive. I had the same idea of running multiple containers, since I'd only need two or three (for now) and I have plenty of CPU/RAM headroom on my NAS. However, I have been told by others that it would start using up more resources and overhead. I have a feeling they overestimate how much resources the qBittorrentVPN container uses on my NAS. Currently, it's using less than 4% CPU and about 2.6GB out of 8GB total RAM. Spread across 2–3 containers, it ought to be fine, don't you think? I just need to make sure I set up the port mappings on each one correctly. I tried doing it last week and couldn't get both qBittorrentVPN containers running at the same time because it seems like they have some hard-coded ports that cannot be changed in `docker-compose.yml`, causing conflicts. I should probably post that issue in the qBittorrentVPN forum.

I apologize for sounding impatient. I did not mean to sound ungrateful for the work that you put in these images nor insensitive to your busy life. Indeed, I am grateful for your willingness to help a poor newbie with his trivial issues. Excellent, thank you for the clarification. I'm guessing ruTorrent needs RPC2, then? If so, I'll leave it enabled. @Cat_Seeder Thank you very much for your help, as well, but I'm afraid most of what you have said goes a bit over my head. I mean, I understand the idea of using SSDs to cache data, but making sure my "cgroups" aren't limiting resources? No idea how to determine that or even what cgroups are. Anyway, my issues with the WebUI being unresponsive are with qBittorrentVPN, thus the reason I'm attempting to use rTorrentVPN instead. (Because I've heard it can handle a larger number of torrents.) Still, I may check out that optimizing rTorrent link you provided if it turns out that rTorrent does, indeed, cope well with 1,600+ torrents. Alright, I gave this a shot, but I'm afraid it didn't help. Even deleted everything in that /config folder except /config/openvpn to let it re-create everything. Still no help. I will say that I have discovered at least part of the problem. In my supervisord.log file, you may have noticed that I set up a volume map of /volume2/media:/data. This poses a problem with your rTorrentVPN image whereas it didn't with qBittorrentVPN. Why? I'm not sure, but I think it has to do with changing permissions or indexing or whatever. You see, In my /volume2/media is a folder called /dockervolumes, and that's where all of my docker container configs and such reside. This includes Plex. Well, /volume2/media/dockervolumes/plex/config/Library/Application Support/Plex Media Server contains nearly 800,000 files and folders. I've no idea what it's all for, but I'm sure a great deal of that is for metadata, thumbnails, etc. And it probably could use some cleanup somehow, but I don't know how to do so without messing things up. And this is in addition to another folder under /volume2/media that contains almost 140,000 files and folders itself. So, I edited my docker-compose.yml file to only have several volume mappings rather than just the one, overarching volume mapping of /volume2/media:/data. Each of the new volume mappings points to just those folders that I need rTorrent to have access to. Once I did another container re-creation with these new mappings, it seems rTorrent and ruTorrent start up fine. (Well, except for rTorrent complaining about ffmpeg with "screenshots: Plugin will not work. rTorrent user can't access external program (ffmpeg)." But I don't think that's necessary.) Now, I just need to figure out how to copy over my 1,600 .torrent files from qBittorrent to rTorrent while keeping their download locations intact and such. Then we'll see whether or not rTorrent really can handle that kind of load. Again, thank you guys so much for your help in this matter.

So, nothing, @binhex? I posted the requested file, yet I've not received a response. I apologize if I seem impatient. It's just that your qBittorrent-vpn image appears to have a great deal of trouble handling my 1,600+ torrents (at least, via its WebUI) and it's getting worse the more torrents I add to it, so I'd really like to move them all to one that—I'm told—should be able to handle up to 6,000 torrents. i.e., your rTorrent-vpn image. I'll re-attach it to this post. As a side note, because I am still relatively new to this, I don't know what `ENABLE_AUTODL_IRSSI` is for, as well as `ENABLE_RPC2`. Could someone please explain those to me so I know whether or not I should have them enabled? rtorrent.rc

Certainly. Here's the file. I did not see any personal info in it to censor, so I didn't edit it. Thank you for looking into this. rtorrent.rc

Good evening. I have been using the qBittorrentVPN image for some time now, but it appears to be choking more and more lately. Probably because I have over 1,600 torrents in it. (I get the "qBitorrent client is not reachable" message.) And that number is only going to go up steadily over time. I've heard that rTorrent can handle up to 5,000–6,000 torrents before choking, so I attempted to implement BinHex's rTorrentVPN image. Unfortunately, I cannot seem to get it working and was hoping someone here could help me. It seems that it times out while attempting to start rTorrent. I'm attaching my log file (edited to remove my email address and VPN password, natch) in the hopes that it might shed some light on what's going on. Could someone please help me to diagnose and fix this? supervisord.log

Good afternoon. This may not be the best place to ask for help, so if someone could kindly point me in the right direction, I'd much appreciate it. I've been using Transmission on my Synology NAS for quite some time now and have somewhat recently added Sonarr and Radarr to allow for automated TV show and movie downloading. When I had a recent problem with a movie not being imported into Radarr, I was told on the Discord chat that I should probably dump Transmission and go with something like this Docker image. I am brand-spankin'-new to Docker. I barely know how to install it on my Synology through their package manager. Attempting to get this QbittorrentVPN image installed is causing me nothing but grief. Is there a relatively easy step-by-step tutorial on how to get this working on Synology DSM? I do have some Linux CLI experience and will employ it to get this working, if necessary. However, DSM seems to have a Docker package already and allows for installing images from Docker Hub. Thus, I'd rather go that route, if possible. Also, with all of the images out there that seem to do the same thing (Deluge, Rtorrent, Qbittorrent, etc.), I'm not certain if this Qbittorrent one is the right one for me. I guess it all comes down to UI and feature preference? Is there a comparison chart or something so I can make a more informed decision between them? Please point me out to me some sort of guide or tutorial on getting this installed and running on Synology with DSM 6.2.1.