3.3.0 Stalled my torrents

[cheesyisgod]

Just upgraded to 3.3.0 from 3.2.5, all torrents were working and downloading up till 1 hour ago, I updated qbittorrent and now only 3 downloads are active the rest have stalled.

30/11/2015 10:06 - External IP: 92.28.xxx.xx
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - 'xxxxxxxxxxxxxxxx' resumed. (fast resume)
30/11/2015 10:06 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/22714
30/11/2015 10:06 - qBittorrent is successfully listening on interface :: port: TCP/22714
30/11/2015 10:06 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/22714
30/11/2015 10:06 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/22714
30/11/2015 10:06 - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433
30/11/2015 10:06 - qBittorrent is successfully listening on interface :: port: TCP/22714
30/11/2015 10:06 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433
30/11/2015 10:06 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/22714
30/11/2015 10:06 - Options were saved successfully.
30/11/2015 10:06 - GeoIP database loaded. Type: GeoLite2-Country. Build time: Tue Nov 3 23:05:56 2015.
30/11/2015 10:06 - Embedded Tracker [OFF]
30/11/2015 10:06 - Encryption support [ON]
30/11/2015 10:06 - Local Peer Discovery support [ON]
30/11/2015 10:06 - PeX support [ON]
30/11/2015 10:06 - DHT support [ON]
30/11/2015 10:06 - Anonymous mode [ON]
30/11/2015 10:06 - HTTP User-Agent is 'qBittorrent v3.3.0'
30/11/2015 10:06 - Peer ID: -qB3300-
30/11/2015 10:06 - qBittorrent is trying to listen on any interface port: 22714
30/11/2015 10:06 - qBittorrent v3.3.0 started

[Buck Bundy]

Same here... everything was working great with 3.2.5 and now cannot connect to any public tracker.

Everything just stalls and every tracker's status is "Not Working".

EDIT: Rolled back to 3.2.5 and everything fine again.

[snutz]

Same problem here.  I haven't tried going back to 3.2.5 yet.  Didn't the 3.3 installer say that one couldn't revert to earlier versions?

[ciaobaby]

There are details in the thread of how to revert.

[XerBlade]

I reverted to 3.2.5 and this issue is still persisting.

It got rid of the annoying "There is no disk in the drive" thing that happened on every start of the program even after rebooting, though.

Short version: it seems I will have no choice but to switch to another client if I want to, you know, be able to actually use torrents.

[How did this make it to stable release exactly?]

[ciaobaby]

I reverted to 3.2.5 and this issue is still persisting.

Which would appear to demonstrate that it is a Windows problem rather than something specific to qbittorrent.

What storage devices does Windows recognise, and what drive letter is assigned to DR3?

[Nemo]

No issues here at all where im running it for days straight, except the ''drive'' thing that only happened with the RC (which is being observed). See here: https://github.com/qbittorrent/qBittorrent/issues/4190

reverted to 3.2.5 and this issue is still persisting.

I did (and always advice) a clean installation because its a big change (especially ''under the hood'') compared to the v3.2.x tree. If it was an update lets say v3.2.6 then updating shouldn't be an issue I assume. You should have made a backup from your settings from v3.2.5 before you did an update. You get a warning dialog before installing v3.3.0 that you can't revert in most cases, because of the reason above.

[How did this make it to stable release exactly?]

We don't have hundreds of testers to test everything, everyone uses qBittorrent different so problems might occur (of course we hope nothing of this happens). If I want I can find issues with every client, its not that hard. But some don't understand this and expect that it must be bug free or anything like that. Thats why we have the bugtracker for this. Its not like its not fixable.

[ThyTorrenter]

[quote="ciaobaby"]
There are details in the thread of how to revert.
[/quote]

Sorry, but which thread? Can't find it.

[ciaobaby]

The release thread for 3.3.0

index.php/topic,3684.0.html

[ThyTorrenter]

Perfect, thanks a lot.

[snutz]

Reverted to 3.2.5 and things are working again.  Thanks!

[Seedthis]

Had the issue myself on Windows 10 x64. I'm not the type of guy to give up so easily. Turned out it was a mixture of the new 3.3.0 settings files that are incompatible with prior versions of qBt and the security suite that runs on that computer (Eset Smart Security 9).

Instead of deleting all the settings and re-adding truck loads of torrents i just deleted "C:\Users\YourName\AppData\Roaming\qBittorrent\qBittorrent.ini". It means that i had to recreate all the client config.

Upon next restart Eset popped a window to accept network traffic for qBittorrent.exe (although i already authorized it). After that i was connectable again and torrents went back seeding. I tried putting back my old qBittorrent.ini file and all torrents where stalled again.

Everything else is fine since doing the config again.

[tagor]

3.3.1 Stalled my torrents. Reverted to 3.2.5 - works fine. Uninstalled completele, then installed 3.3.1 again - there are stalled torrents still. Should reroll to 23.2.5 and waiting for 3.3.2?

[Nemo]

Torrents from private trackers? If so then they need to whitelist qBittorrent first in order to be used.

[tagor]

well, I've tried both private and pubplic trackers. And still same trackers work just fine with 3.2.5