[Support] binhex - qBittorrentVPN


Recommended Posts

On 4/20/2021 at 7:14 PM, ds123 said:

I can't download torrents from their URLs. Nothing happens when I try to do that.

I looked at the logs file and all I see is the following log -

"Downloading '{someTorrentUrl}', please wait..."

 

Happens also in linuxserver docker.

 

Any idea? I'm using the default settings, only disabled the vpn and changed the port via the web ui.

 

 

 

I'm seeing the same thing on a new install. Can't seem to figure out at all what's going on, no other logs seem to be displaying any errors.

Link to comment
9 hours ago, mDrewitt said:

 

I'm seeing the same thing on a new install. Can't seem to figure out at all what's going on, no other logs seem to be displaying any errors.

 

https://github.com/qbittorrent/qBittorrent/issues/11150

 It fails because qbittorrent doesn't have access to private trackers.

 

I found a workaround - install the Jackett docker, then configure an indexer for the private tracker, then enable the Jackett search plugin in qbittorrent, search and download from there. 

Edited by ds123
Link to comment
9 hours ago, mDrewitt said:

 

I'm seeing the same thing on a new install. Can't seem to figure out at all what's going on, no other logs seem to be displaying any errors.

did you configure the downloads location in qbittorrent?, if not it will be attempting to download to a location that doesnt exist, go to 'Options/<downloads tab>/Default Save Path' and set it to /data, then stop and start the torrent

Link to comment
On 4/3/2021 at 1:52 PM, barnito said:

I would try to give each instance their own IP on your network using br0, see if that changes anything

image.thumb.png.05d0f01847624ab50b2289a2fc293857.png

 

Sorry for the late reply, just got myself some time to test this again tonight. It's not working either. Has anyone got multiple Sonarr or Radarr instances successfully passed through this container without them all defaulting to the same port? (8989 and 8989, for example).

Link to comment

Hi

 

Trying to install this to my QNAP NAS, but I get this error:

 

2021-04-24 00:05:02,973 DEBG 'start-script' stdout output:                                                                                                   

2021-04-24 00:05:02 sitnl_send: rtnl: generic error (-101): Network is unreachable                                                                           

2021-04-24 00:05:02 ERROR: Linux route add command failed    

 

How to fix?

 

Here is my full install log:

 

Spoiler

Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
  https://hub.docker.com/u/binhex/

2021-04-24 00:04:52.833288 [info] System information Linux 950b871b8f2d 4.14.24-qnap #1 SMP Tue Apr 6 05:12:32 CST 2021 x86_64 GNU/Linux
2021-04-24 00:04:52.875263 [info] OS_ARCH defined as 'x86-64'
2021-04-24 00:04:52.919605 [info] PUID defined as '0'
2021-04-24 00:04:52.968948 [info] PGID defined as '0'
2021-04-24 00:04:53.359163 [info] UMASK defined as '000'
2021-04-24 00:04:53.402682 [info] Permissions already set for volume mappings
2021-04-24 00:04:53.452659 [info] Deleting files in /tmp (non recursive)...
2021-04-24 00:04:53.538848 [info] VPN_ENABLED defined as 'yes'
2021-04-24 00:04:53.585046 [info] VPN_CLIENT defined as 'openvpn'
2021-04-24 00:04:53.634605 [info] VPN_PROV defined as 'custom'
2021-04-24 00:04:53.686795 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/AB-UDP.ovpn
2021-04-24 00:04:53.794590 [info] VPN remote server(s) defined as 'AB-uk.dns2use.com,'
2021-04-24 00:04:53.835573 [info] VPN remote port(s) defined as '53,'
2021-04-24 00:04:53.874256 [info] VPN remote protcol(s) defined as 'udp,'
2021-04-24 00:04:53.919935 [info] VPN_DEVICE_TYPE defined as 'tun0'
2021-04-24 00:04:53.970075 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2021-04-24 00:04:54.022451 [info] LAN_NETWORK defined as '192.168.1.0/24'
2021-04-24 00:04:54.068088 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2021-04-24 00:04:54.115081 [info] VPN_USER defined as <removed>
2021-04-24 00:04:54.164756 [info] VPN_PASS defined as <removed>
2021-04-24 00:04:54.208026 [info] ENABLE_PRIVOXY defined as 'yes'
2021-04-24 00:04:54.259007 [info] VPN_INPUT_PORTS defined as '1234'
2021-04-24 00:04:54.306304 [info] VPN_OUTPUT_PORTS defined as '5678'
2021-04-24 00:04:54.351089 [info] WEBUI_PORT defined as '9091'
2021-04-24 00:04:54.463138 [info] Starting Supervisor...
2021-04-24 00:04:54,720 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2021-04-24 00:04:54,720 INFO Set uid to user 0 succeeded
2021-04-24 00:04:54,723 INFO supervisord started with pid 7
2021-04-24 00:04:55,726 INFO spawned: 'shutdown-script' with pid 168
2021-04-24 00:04:55,728 INFO spawned: 'start-script' with pid 169
2021-04-24 00:04:55,730 INFO spawned: 'watchdog-script' with pid 170
2021-04-24 00:04:55,731 INFO reaped unknown pid 8 (exit status 0)
2021-04-24 00:04:55,740 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2021-04-24 00:04:55,740 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-04-24 00:04:55,740 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-04-24 00:04:55,740 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-04-24 00:04:55,741 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2021-04-24 00:04:55,786 DEBG 'start-script' stdout output:
[warn] Username contains characters which could cause authentication issues, please consider changing this if possible

2021-04-24 00:04:55,915 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2021-04-24 00:04:55,920 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2021-04-24 00:04:55,934 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2021-04-24 00:04:55,940 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2021-04-24 00:04:55,945 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2021-04-24 00:04:55,950 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2021-04-24 00:04:55,955 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2021-04-24 00:05:01,397 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2021-04-24 00:05:01,399 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.14.24-qnap

2021-04-24 00:05:01,399 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2021-04-24 00:05:01,401 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2021-04-24 00:05:01,401 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

2021-04-24 00:05:01,413 DEBG 'start-script' stdout output:
[info] Default route for container is 10.0.3.1

2021-04-24 00:05:01,430 DEBG 'start-script' stdout output:
[info] Docker network defined as    10.0.3.0/24

2021-04-24 00:05:01,434 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2021-04-24 00:05:01,436 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2021-04-24 00:05:01,437 DEBG 'start-script' stdout output:
default via 10.0.3.1 dev eth0 
10.0.3.0/24 dev eth0 proto kernel scope link src 10.0.3.2 
192.168.1.0/24 via 10.0.3.1 dev eth0 
broadcast 10.0.3.0 dev eth0 table local proto kernel scope link src 10.0.3.2 
local 10.0.3.2 dev eth0 table local proto kernel scope host src 10.0.3.2 
broadcast 10.0.3.255 dev eth0 table local proto kernel scope link src 10.0.3.2 

2021-04-24 00:05:01,437 DEBG 'start-script' stdout output:
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 
--------------------

2021-04-24 00:05:01,513 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2021-04-24 00:05:01,515 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 10.0.3.0/24 -d 10.0.3.0/24 -j ACCEPT
-A INPUT -s 73.254.102.202/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 9091 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 9091 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 1234 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 1234 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 10.0.3.0/24 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 10.0.3.0/24 -i eth0 -p tcp -m tcp --sport 5678 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 10.0.3.0/24 -d 10.0.3.0/24 -j ACCEPT
-A OUTPUT -d 73.254.102.202/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 9091 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 9091 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 1234 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 1234 -j ACCEPT
-A OUTPUT -s 10.0.3.0/24 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8118 -j ACCEPT
-A OUTPUT -s 10.0.3.0/24 -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --dport 5678 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2021-04-24 00:05:01,516 DEBG 'start-script' stdout output:
--------------------

2021-04-24 00:05:01,517 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2021-04-24 00:05:01,526 DEBG 'start-script' stdout output:
2021-04-24 00:05:01 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.

2021-04-24 00:05:01,526 DEBG 'start-script' stdout output:
2021-04-24 00:05:01 WARNING: file 'credentials.conf' is group or others accessible
2021-04-24 00:05:01 OpenVPN 2.5.1 [git:makepkg/f186691b32e68362+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 24 2021
2021-04-24 00:05:01 library versions: OpenSSL 1.1.1k  25 Mar 2021, LZO 2.10

2021-04-24 00:05:01,602 DEBG 'start-script' stdout output:
2021-04-24 00:05:01 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2021-04-24 00:05:01,604 DEBG 'start-script' stdout output:
2021-04-24 00:05:01 TCP/UDP: Preserving recently used remote address: [AF_INET]73.254.102.202:53
2021-04-24 00:05:01 UDP link local: (not bound)
2021-04-24 00:05:01 UDP link remote: [AF_INET]73.254.102.202:53

2021-04-24 00:05:01,751 DEBG 'start-script' stdout output:
2021-04-24 00:05:01 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1550'
2021-04-24 00:05:01 WARNING: 'auth' is used inconsistently, local='auth SHA1', remote='auth [null-digest]'
2021-04-24 00:05:01 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'

2021-04-24 00:05:01,751 DEBG 'start-script' stdout output:
2021-04-24 00:05:01 [Secure-Server] Peer Connection Initiated with [AF_INET]73.254.102.202:53

2021-04-24 00:05:02,971 DEBG 'start-script' stdout output:
2021-04-24 00:05:02 TUN/TAP device tun0 opened
2021-04-24 00:05:02 /root/openvpnup.sh tun0 1500 1552   init

2021-04-24 00:05:02,973 DEBG 'start-script' stdout output:
2021-04-24 00:05:02 sitnl_send: rtnl: generic error (-101): Network is unreachable
2021-04-24 00:05:02 ERROR: Linux route add command failed
2021-04-24 00:05:02 sitnl_send: rtnl: generic error (-101): Network is unreachable
2021-04-24 00:05:02 ERROR: Linux route add command failed
2021-04-24 00:05:02 Initialization Sequence Completed

 

Link to comment
On 4/22/2021 at 5:18 AM, binhex said:

did you configure the downloads location in qbittorrent?, if not it will be attempting to download to a location that doesnt exist, go to 'Options/<downloads tab>/Default Save Path' and set it to /data, then stop and start the torrent

 

Ya I made sure that the downloads folder is set and the folder exists. 

 

Maybe I'm misunderstanding, but I should be able to add something using a magnet link on the Web UI right?  I put in the link, and hit download, the window closes then nothing ever shows up in the list and the qBittorrent.log just says
 

Downloading '{URL}', please wait...

 

But that's where it ends. It never does anything.

 

For reference, I setup the container like so:

  1. Added from the CA
  2. Set the VPN username/password
  3. Set VPN to custom and openvpn
  4. Deleted the existing 8080 port for the Web UI (using that for Nginx) and added a new port mapping for 8090
  5. Set the port WEBUI_PORT to 8090
  6. Saved, copied the ovpn file to the correct folder and started the container
  7. Setup the download folder, and went into the file system and did a mkdir so it exists
  8. Confirmed that it can search and see the VPN connecting and getting a proper external IP
  9. Open -> Add Torrent Link

Then I get the above message in the log and nothing starts. Tried multiple links all the same result

Link to comment
On 4/21/2021 at 8:28 PM, TexasUnraid said:

Just an observation, I have been having some random blackouts and the server randomly shutting down recently (UPS died the other day).

 

Each time the server does an unclean shutdown, Qbittorrent seems to loose all it's settings.

 

I now have a backup of the appdata folder and if I copy it back over the appdata and restart the docker, everything is back to normal.

 

Any idea why the settings are erased on unclean shutdown?

I'm experiencing the same exact problem

Were you able to find a reason, or solution?

Link to comment
1 minute ago, timmyx said:

I'm experiencing the same exact problem

Were you able to find a reason, or solution?

No, i just resorted to making a copy of the qbittorrent folder in appdata (named it -backup) and I just copy it over the existing qbittorrent folder and restart the docker. I should setup an rsync job so I don't loose any new seeds/downloads but have not been using it much lately so kinda dealing with it.

Link to comment
8 minutes ago, TexasUnraid said:

No, i just resorted to making a copy of the qbittorrent folder in appdata (named it -backup) and I just copy it over the existing qbittorrent folder and restart the docker. I should setup an rsync job so I don't loose any new seeds/downloads but have not been using it much lately so kinda dealing with it.

 

Yeah I do my backups too, will have to figure out how to setup an automated workaround for this

maybe adding an rsync/rclone job at the startup of the array to copy the backup config file to the qbittorrent folder idk

Link to comment
Just now, timmyx said:

 

Yeah I do my backups too, will have to figure out how to setup an automated workaround for this

maybe adding an rsync/rclone job at the startup of the array to copy the backup config file to the qbittorrent folder idk

Yeah, that would work, I think there is just one file that needs to be replaced but it is simpler for me to just copy the whole folder over.

  • Like 1
Link to comment

Anyone else getting very high latency and low speeds with PIA's wireguard?

 

Here's a speedtest from within an unRAID VM:

$ curl -s https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py | python -
Retrieving speedtest.net configuration...
Testing from Optimum Online (XX.XX.XXX.XX)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Syndeo Solutions (Springfield, MO) [1748.93 km]: 48.05 ms
Testing download speed................................................................................
Download: 103.52 Mbit/s
Testing upload speed................................................................................................
Upload: 33.52 Mbit/s

 

And here it is on the same machine from within the container (configured like so):

# grep Endpoint /mnt/cache/appdata/binhex-qbittorrentvpn/wireguard/wg0.conf
Endpoint = bahamas.privacy.network:1337

 

# docker exec -it binhex-qbittorrentvpn sh
sh-5.1# curl -s https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py | python -
Retrieving speedtest.net configuration...
Testing from Redcom-Internet (XX.XXX.XXX.XX)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Gold Data (Miami, FL) [295.19 km]: 1927.194 ms
Testing download speed................................................................................
Download: 8.65 Mbit/s
Testing upload speed......................................................................................................
Upload: 7.85 Mbit/s

 

I tried adding the following to Extra Parameters per the guide but it doesn't seem to make a difference.

--sysctl="net.ipv4.conf.all.src_valid_mark=1"

 

Link to comment

Not sure what happened but randomly my privoxy stopped working. I've tried to force update the container and it still is giving errors. What could be stopping privoxy from starting?

Quote

2021-05-04 11:03:20,390 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2021-05-04 11:03:21,415 DEBG 'watchdog-script' stdout output:
[debug] Waiting for Privoxy process to start
[debug] Re-check in 1 secs...
[debug] 11 retries left

2021-05-04 11:03:22,424 DEBG 'watchdog-script' stdout output:
[debug] Waiting for Privoxy process to start
[debug] Re-check in 1 secs...
[debug] 10 retries left

2021-05-04 11:03:23,432 DEBG 'watchdog-script' stdout output:
[debug] Waiting for Privoxy process to start
[debug] Re-check in 1 secs...
[debug] 9 retries left

 

Link to comment
16 hours ago, Spikerman said:

Not sure what happened but randomly my privoxy stopped working. I've tried to force update the container and it still is giving errors. What could be stopping privoxy from starting?

 

I also had issues yesterday, but it looks like it's working fine this morning. Hopefully it's the same for you.

Link to comment
23 hours ago, LeGourmand said:

I also had issues yesterday, but it looks like it's working fine this morning. Hopefully it's the same for you.

 

12 hours ago, Spikerman said:

Mine seemed to start working today as well, its been broken for days on my system.

then you know the issue is vpn provider related, i have made zero code changes, last release was 19 days ago.

Link to comment

Hi

I have Docker installed on a Windows 10 PC.
arch-bittorrentvpn runs, I can access qBit locally but I found that I could also access qBit outside on my LAN.

 

supervisord.log in Pastebin:
https://pastebin.com/u2Ebffhd

 

I see a lines; modprobe: FATAL: Module tun not found in directory /lib/modules/5.4.72-microsoft-standard-WSL2

and; modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.4.72-microsoft-standard-WSL2

 

I have tried on a PC that has had Docker running for a few months and also installed Docker fresh on another machine. WSL2 installed at the same time.

 

Thanks

Link to comment
On 5/6/2021 at 3:13 AM, binhex said:

 

then you know the issue is vpn provider related, i have made zero code changes, last release was 19 days ago.

I also rebooted my unraid box. It may have been something hung there as it was not working before the reboot as well.

 

Very strange, in the logs the vpn shows its connected and no errors. Will make a new post with more info if it ever happens again.

Link to comment
21 hours ago, mmag05 said:

My IP and port keep changing and each time this happens seeding stops.  Is there any action I can take to correct this behavior?

vpn providers using dhcp so you will nearly always get a different ip and port if the vpn drops and re-establishes, ive just tested this by forcing a drop of the vpn connection, and if i wait i can see the connection comes up (with different ip and port) and qbittorrent re-registers with the tracker and seeding resumes with no issue, are you seeding to a private torrent site?.

Link to comment

Having a strange issue for the last couple of weeks.  Sonarr will identify a tv episode and correctly send the download request to qbittorent.  But then when the show is done downloading it just goes away.  It's like Sonarr is not correctly seeing the completed download and importing it into Plex like it should.  And it's very random.  Most shows work fine but there's always a couple random ones that don't work.  Binhex I'm running your version of Sonarr also.  Is this a Sonarr issue or qbittorent issue?

Link to comment
3 minutes ago, hahler2 said:

Having a strange issue for the last couple of weeks.  Sonarr will identify a tv episode and correctly send the download request to qbittorent.  But then when the show is done downloading it just goes away.  It's like Sonarr is not correctly seeing the completed download and importing it into Plex like it should.  And it's very random.  Most shows work fine but there's always a couple random ones that don't work.  Binhex I'm running your version of Sonarr also.  Is this a Sonarr issue or qbittorent issue?

im not aware of either of these apps having this issue, i use both myself and havent seen this, i would double check its not this issue: Q4 from this link:-https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Link to comment
10 minutes ago, hahler2 said:

Double checked everything.  I do not believe it to be a path issue.  They look the same to me.  And I haven't changed anything in months and it's always worked fine.

one last thing to check then, what have you got defined for qbittorrent web ui/options/bittorrent tab/seeding limits?, you need to ensure its only set to 'pause torrent' (if enabled).

Link to comment

 

2 hours ago, binhex said:

one last thing to check then, what have you got defined for qbittorrent web ui/options/bittorrent tab/seeding limits?, you need to ensure its only set to 'pause torrent' (if enabled).

 

Ah.  I have that set to remove the torrent and the files after the ratio reaches 1.0.  That way I don't have to constantly go through and delete files from qbitorrent and the download folder on my server.  I'll change that to pause and see if that fixes it.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.