I have qBittorrent and PIA, with the killswitch enabled and my qBittorrent linked to the VPN network interface, so whenever my VPN disconnects (which is usually 2-3 times per day) my qBittorrent stops downloading immediately.
However when the VPN reconnects, my downloads do not restart. They get stuck on "stalled" until I restart qBittorrent, after which everything has to "check" and then downloading usually resumes fine.
I can't find anything online about how to fix this, any one had this problem and found a way around it? I don't want to have to restart the client multiple times a day since the checking of the torrents usually takes ages
Downloads not restarting after internet reconnect
-
there
Re: Downloads not restarting after internet reconnect
Hi Sshaun_10
I am also with PIA, have the exact same problem as you. I have noticed that it mostly seems to happen when I torrent. I get about 15 mins between resets, and have my line often go down more than 5 time in an hour. This is my last year with PIA.
I am here to find the same answer and fix as you. Sad but glad to find out that it is just not me with this issue. I also had this same issue with other ISPs too
I am also with PIA, have the exact same problem as you. I have noticed that it mostly seems to happen when I torrent. I get about 15 mins between resets, and have my line often go down more than 5 time in an hour. This is my last year with PIA.
I am here to find the same answer and fix as you. Sad but glad to find out that it is just not me with this issue. I also had this same issue with other ISPs too
-
there
Re: Downloads not restarting after internet reconnect
Hi again Sshaun_10,
Are you using Avira? If so Right click on Icon and untick Enable Real-time Protection. Now start you torrents again. I have just had a stable 3 hour stint which is unprecedented, or PIA have fixed stuff on their side?
Are you using Avira? If so Right click on Icon and untick Enable Real-time Protection. Now start you torrents again. I have just had a stable 3 hour stint which is unprecedented, or PIA have fixed stuff on their side?
-
coolio2013
Re: Downloads not restarting after internet reconnect
[quote="Sshaun_10"]
I have qBittorrent and PIA, with the killswitch enabled and my qBittorrent linked to the VPN network interface, so whenever my VPN disconnects (which is usually 2-3 times per day) my qBittorrent stops downloading immediately.
However when the VPN reconnects, my downloads do not restart. They get stuck on "stalled" until I restart qBittorrent, after which everything has to "check" and then downloading usually resumes fine.
I can't find anything online about how to fix this, any one had this problem and found a way around it? I don't want to have to restart the client multiple times a day since the checking of the torrents usually takes ages
[/quote]
If everything else is right, it could help to change the listening port for incoming connections. The green ball will change to yellow and should become green again, after reaching a certain amount of nodes. D/L should start, after most I/O jobs have been completed (View/Statistics, for me it starts around 100 usually). For some reason, qbt or libtorrent is checking torrents all the time and reading huge amounts of data, even paused torrents.
HTH.
I have qBittorrent and PIA, with the killswitch enabled and my qBittorrent linked to the VPN network interface, so whenever my VPN disconnects (which is usually 2-3 times per day) my qBittorrent stops downloading immediately.
However when the VPN reconnects, my downloads do not restart. They get stuck on "stalled" until I restart qBittorrent, after which everything has to "check" and then downloading usually resumes fine.
I can't find anything online about how to fix this, any one had this problem and found a way around it? I don't want to have to restart the client multiple times a day since the checking of the torrents usually takes ages
[/quote]
If everything else is right, it could help to change the listening port for incoming connections. The green ball will change to yellow and should become green again, after reaching a certain amount of nodes. D/L should start, after most I/O jobs have been completed (View/Statistics, for me it starts around 100 usually). For some reason, qbt or libtorrent is checking torrents all the time and reading huge amounts of data, even paused torrents.
HTH.
-
Switeck
Re: Downloads not restarting after internet reconnect
[quote="coolio2013"]For some reason, qbt or libtorrent is checking torrents all the time and reading huge amounts of data, even paused torrents.[/quote]Sounds like qBT bugs honestly.
It doesn't sound exactly like some force recheck qBT bugs I've read about at github qBT issues...but it sounds similar.
Usually after a bad crash, qBT may recheck some/all torrents loaded in it. This can take a very long time with enough torrents on a slow, large HDD.
So the kill switch for the VPN may be glitching qBT up in some way, enough so qBT tries to recheck torrents?
It doesn't sound exactly like some force recheck qBT bugs I've read about at github qBT issues...but it sounds similar.
Usually after a bad crash, qBT may recheck some/all torrents loaded in it. This can take a very long time with enough torrents on a slow, large HDD.
So the kill switch for the VPN may be glitching qBT up in some way, enough so qBT tries to recheck torrents?
-
coolio2013
Re: Downloads not restarting after internet reconnect
Often very difficult to tell, except for arvidn or sledge and some others DEEP inside the sources.Switeck wrote:Sounds like qBT bugs honestly.coolio2013 wrote:For some reason, qbt or libtorrent is checking torrents all the time and reading huge amounts of data, even paused torrents.
Yes, but then the status is not 'Paused'. It will be checked (LOG: Fast resume data rejected...).It doesn't sound exactly like some force recheck qBT bugs I've read about at github qBT issues...but it sounds similar.
Usually after a bad crash, qBT may recheck some/all torrents loaded in it. This can take a very long time with enough torrents on a slow, large HDD.
Several bugs have been opened on that. Seems it is a minor issue for devs, but it is a huge issue for me (due to slow network shares).
This is somewhat similar https://github.com/qbittorrent/qBittorrent/issues/4456, but my files exist.
This https://github.com/qbittorrent/qBittorrent/issues/6754 is by myself. I closed it when I came to the conclusion that it is a duplicate.
This https://github.com/arvidn/libtorrent/issues/1869 is a little weird and on Deluge.
No, usually the killswitch just removes the IP from the interface or disable the interface, so qbt won't get any data.So the kill switch for the VPN may be glitching qBT up in some way, enough so qBT tries to recheck torrents?
I have no idea what causes qbt to start huge amounts of IO tasks after reconnect and changing the port.
Btw, the status doesn't change to 'Checking...', torrents remain on previous status in the GUI, but files are just hashed or at least existance is checked, see screenshot in my https://github.com/qbittorrent/qBittorrent/issues/6754.
Wondering if changing the port helps Sshaun_10?
-
Sshaun_10
Re: Downloads not restarting after internet reconnect
Changing the listening ports doesn't seemed to have helped. Tried turning off the VPN killswitch and that didn't work either. It's really frustrating because my PIA disconnects and reconnects multiple times a day. Maybe I should just change VPN providers? I really don't want to switch torrent clients since qbt has my favorite layout.
-
coolio2013
Re: Downloads not restarting after internet reconnect
[quote="Sshaun_10"]
Changing the listening ports doesn't seemed to have helped. Tried turning off the VPN killswitch and that didn't work either. It's really frustrating because my PIA disconnects and reconnects multiple times a day. Maybe I should just change VPN providers? I really don't want to switch torrent clients since qbt has my favorite layout.
[/quote]
Which version are you using? OS?
You'll have to try others, if nothing helps.
PIA is one of the more widely used. I did have about 10 reconnects to my VPN in the last 2 days, not any issue with qbt 3.3.14 on Windows.
Changing the listening ports doesn't seemed to have helped. Tried turning off the VPN killswitch and that didn't work either. It's really frustrating because my PIA disconnects and reconnects multiple times a day. Maybe I should just change VPN providers? I really don't want to switch torrent clients since qbt has my favorite layout.
[/quote]
Which version are you using? OS?
You'll have to try others, if nothing helps.
PIA is one of the more widely used. I did have about 10 reconnects to my VPN in the last 2 days, not any issue with qbt 3.3.14 on Windows.
-
experimental
Re: Downloads not restarting after internet reconnect
I had the same problem I use the script over here at https://www.privateinternetaccess.com/forum/discussion/23542/powershell-port-forwarding-for-utorrent-qbittorrent-other-for-new-api?new=1
It uses openvpn to connect, and the scripts check to make sure qbitorrent isn't stalled, and can request port forwarding. It's written in powershell so you can follow and see what it does.
It uses openvpn to connect, and the scripts check to make sure qbitorrent isn't stalled, and can request port forwarding. It's written in powershell so you can follow and see what it does.
Re: Downloads not restarting after internet reconnect
EDIT: This failed, but I think I figured out why.
qbittorrent does not release and bind to the new config of the Network Interface.
To explain, my Network Interface is "PureVPN_1" in qbittorrent, but if I disconnect the PureVPN, the next time it connects, it will update with another configuration, "PureVPN_2". I don't believe that qbittorrent does anything with this update, nor do I think it even notices it. I do not believe it reads or updates the configuration so it is unable to bind to them. The result is no matter how you try to reannounce, it fails, leaving only one option, to restart.
I was having some similar issues with split tunneling. If the VPN was disconnected for any reason, it would stall the torrents (as intended) but when the connection was reestablished the torrent app would fail to reconnect (even with "forced reannounce").
I am using qbittorrent v5.0.5, PureVPN v14.7.0.13, Comodo Internet Security 2025 Pro v12.3.4.8162
How I got qbittorrent to automatically resume following a PureVPN disconnection...
Settings...
Comodo HIPS turned OFF
Whitelist "Do Not Block" each notification of C:\Windows\System32\conhost.exe or powershell scripts that pops up. Double check the notification list and "Unblock Applications" to make sure you did not miss any. (more to follow below)
PureVPN > Settings > General > Enable IKS = OFF
PureVPN > Settings > Protocol > Automatic Protocol Selection = OFF
PureVPN > Settings > Protocol > Select Protocol > WireGuard (YMMV)
PureVPN > Settings > Protocol > Connect To Fallback = UNCHECKED
PureVPN > Settings > Split Tunneling > Enable Split Tunneling = ON
PureVPN > Settings > Split Tunneling > List of Apps = qbittorrent
Restart.
Qbittorrent > Tools > Options > Advanced > Network Interface = PureVPN_#
This field is only populated when PureVPN is actively connected to its servers. If it's blank, connect to the VPN and refresh.
WARNING: Torrents will ONLY again become active after "reannounce". This can be forced either through the right-click drop down, or selecting stop, then start for the individual selected torrent(s).
What I think was happening:
The virtual network interface (PureVPN_#) regenerates a new one every time PureVPN reestablishes its connection — especially with WireGuard. I noticed this after seeing multiple entries in the network interface list (PureVPN_1, PureVPN_2, etc.). This breaks the qBittorrent bind if it was tied to a now-defunct adapter from the previous session.
After everything seemed to be operating as intended, I checked for leaks... ipleak.net
Command Prompt was helpful to see IP Config... C:\Users\PC>ipconfig /all
This setup acts as a soft kill switch — it blocks torrent traffic when the VPN is down, but doesn’t block internet access system-wide (unlike a full firewall kill switch).
I am currently still seeing scripts being blocked in Comodo. "Unblock Applications", select from the list and unblock (whitelisting them) but I will be setting up a RULE to allow PowerScrips from C:ProgramData\Comodo\Cis\tempscrpt folder.
I have not figured out how to deal with HIPS "active" as of yet, sorry.
qbittorrent does not release and bind to the new config of the Network Interface.
To explain, my Network Interface is "PureVPN_1" in qbittorrent, but if I disconnect the PureVPN, the next time it connects, it will update with another configuration, "PureVPN_2". I don't believe that qbittorrent does anything with this update, nor do I think it even notices it. I do not believe it reads or updates the configuration so it is unable to bind to them. The result is no matter how you try to reannounce, it fails, leaving only one option, to restart.
I was having some similar issues with split tunneling. If the VPN was disconnected for any reason, it would stall the torrents (as intended) but when the connection was reestablished the torrent app would fail to reconnect (even with "forced reannounce").
I am using qbittorrent v5.0.5, PureVPN v14.7.0.13, Comodo Internet Security 2025 Pro v12.3.4.8162
How I got qbittorrent to automatically resume following a PureVPN disconnection...
Settings...
Comodo HIPS turned OFF
Whitelist "Do Not Block" each notification of C:\Windows\System32\conhost.exe or powershell scripts that pops up. Double check the notification list and "Unblock Applications" to make sure you did not miss any. (more to follow below)
PureVPN > Settings > General > Enable IKS = OFF
PureVPN > Settings > Protocol > Automatic Protocol Selection = OFF
PureVPN > Settings > Protocol > Select Protocol > WireGuard (YMMV)
PureVPN > Settings > Protocol > Connect To Fallback = UNCHECKED
PureVPN > Settings > Split Tunneling > Enable Split Tunneling = ON
PureVPN > Settings > Split Tunneling > List of Apps = qbittorrent
Restart.
Qbittorrent > Tools > Options > Advanced > Network Interface = PureVPN_#
This field is only populated when PureVPN is actively connected to its servers. If it's blank, connect to the VPN and refresh.
WARNING: Torrents will ONLY again become active after "reannounce". This can be forced either through the right-click drop down, or selecting stop, then start for the individual selected torrent(s).
What I think was happening:
The virtual network interface (PureVPN_#) regenerates a new one every time PureVPN reestablishes its connection — especially with WireGuard. I noticed this after seeing multiple entries in the network interface list (PureVPN_1, PureVPN_2, etc.). This breaks the qBittorrent bind if it was tied to a now-defunct adapter from the previous session.
After everything seemed to be operating as intended, I checked for leaks... ipleak.net
Command Prompt was helpful to see IP Config... C:\Users\PC>ipconfig /all
This setup acts as a soft kill switch — it blocks torrent traffic when the VPN is down, but doesn’t block internet access system-wide (unlike a full firewall kill switch).
I am currently still seeing scripts being blocked in Comodo. "Unblock Applications", select from the list and unblock (whitelisting them) but I will be setting up a RULE to allow PowerScrips from C:ProgramData\Comodo\Cis\tempscrpt folder.
I have not figured out how to deal with HIPS "active" as of yet, sorry.