Recent Posts

Pages: [1] 2 3 ... 10
1
Windows / Re: Can't Download From One Particular Tracker
« Last post by Switeck on Today at 10:11:08 AM »
They may have banned qBitTorrent recently and/or banned you.
Or they're offline/dead.
You'll need to ask them for more details...
2
Windows / Can't Download From One Particular Tracker
« Last post by ScaryGuy on Today at 09:45:21 AM »
Hi,

I'm using Windows 10 Enterprise and qBittorrent c3.3.12 (32-bit). I use several free and private trackers and I can download from all of them fine except for one of the private trackers. Here's what it says under trackers for one of the torrents I'm trying to download:



Can someone please suggest how I can get torrents from the tracker downloading again?

Thank you.
3
Windows / Re: Outgoing port Min/Max
« Last post by vg8open on Today at 05:43:47 AM »
I think it work somewhat for peer and seed connection.  Below is a traffic capture while I download a torrent.  Port 15000 is the port I use for incoming connection.  It seem like sometime it's sending and receiving data in the 50010 port... 

If I turn on my firewall and only allow port 15000 inbound, and port 50000-50010 outbound for qBittorrent, no TCP tracker can connect.  The status of the tracker stated that it's "Not working".  UDP tracker seem to work fine though.

I am going to submit a ticket...

23:31:17.526139 IP 78.63.147.202.51413 > 192.168.1.2.15000: UDP, length 1028
23:31:17.526464 IP 192.168.1.2.15000 > 78.63.147.202.51413: UDP, length 20
23:31:17.530780 IP 112.205.138.78.8999 > 192.168.1.2.15000: UDP, length 1470
23:31:17.530886 IP 112.205.138.78.8999 > 192.168.1.2.15000: UDP, length 1470
23:31:17.530968 IP 112.205.138.78.8999 > 192.168.1.2.15000: UDP, length 1470
23:31:17.531015 IP 192.168.1.2.15000 > 112.205.138.78.8999: UDP, length 20
23:31:17.531029 IP 112.205.138.78.8999 > 192.168.1.2.15000: UDP, length 1470
23:31:17.531141 IP 112.205.138.78.8999 > 192.168.1.2.15000: UDP, length 1470
23:31:17.531153 IP 192.168.1.2.15000 > 112.205.138.78.8999: UDP, length 20
23:31:17.531389 IP 192.168.1.2.15000 > 112.205.138.78.8999: UDP, length 20
23:31:17.534123 IP 46.166.190.152.52165 > 192.168.1.2.15000: UDP, length 1462
23:31:17.534310 IP 192.168.1.2.15000 > 46.166.190.152.52165: UDP, length 20
23:31:17.537059 IP 46.166.190.152.52165 > 192.168.1.2.15000: UDP, length 1462
23:31:17.537248 IP 46.166.190.152.52165 > 192.168.1.2.15000: UDP, length 1462
23:31:17.537253 IP 192.168.1.2.15000 > 46.166.190.152.52165: UDP, length 20
23:31:17.537459 IP 192.168.1.2.15000 > 46.166.190.152.52165: UDP, length 20
23:31:17.543550 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.543753 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.543761 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 200
23:31:17.543939 IP 192.168.1.2.50010 > 159.192.234.38.50665: tcp 0
23:31:17.545249 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.545348 IP 192.168.1.2.50010 > 159.192.234.38.50665: tcp 0
23:31:17.545565 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.545573 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 200
23:31:17.545788 IP 192.168.1.2.50010 > 159.192.234.38.50665: tcp 0
23:31:17.546248 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.546455 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.546463 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 200
23:31:17.546539 IP 192.168.1.2.50010 > 159.192.234.38.50665: tcp 0
23:31:17.546639 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.546752 IP 192.168.1.2.50010 > 159.192.234.38.50665: tcp 0
23:31:17.547059 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.547355 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.547453 IP 192.168.1.2.50010 > 159.192.234.38.50665: tcp 0
23:31:17.547655 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 1400
23:31:17.547662 IP 159.192.234.38.50665 > 192.168.1.2.50010: tcp 400
23:31:17.547848 IP 192.168.1.2.50010 > 159.192.234.38.50665: tcp 0
23:31:17.557794 IP 93.238.45.140.33154 > 192.168.1.2.15000: UDP, length 533
23:31:17.558021 IP 192.168.1.2.15000 > 93.238.45.140.33154: UDP, length 20
23:31:17.583302 IP 78.235.238.208.57561 > 192.168.1.2.15000: tcp 1460
23:31:17.595835 IP 78.235.238.208.57561 > 192.168.1.2.15000: tcp 1460
23:31:17.595973 IP 192.168.1.2.15000 > 78.235.238.208.57561: tcp 0
23:31:17.599034 IP 192.168.1.2.15000 > 202.166.8.136.8999: UDP, length 37
23:31:17.599120 IP 192.168.1.2.15000 > 173.239.240.69.14710: UDP, length 37
23:31:17.599197 IP 192.168.1.2.15000 > 112.133.167.125.7016: tcp 17
23:31:17.599280 IP 192.168.1.2.15000 > 2.51.119.195.8999: UDP, length 54
23:31:17.599347 IP 192.168.1.2.15000 > 90.88.11.143.55378: tcp 34
23:31:17.681866 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.682050 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.682135 IP 192.168.1.2.15000 > 121.7.133.118.55712: UDP, length 20
23:31:17.682226 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.682334 IP 192.168.1.2.15000 > 121.7.133.118.55712: UDP, length 20
23:31:17.682551 IP 192.168.1.2.15000 > 121.7.133.118.55712: UDP, length 20
23:31:17.682574 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.682581 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.682779 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.682786 IP 192.168.1.2.15000 > 121.7.133.118.55712: UDP, length 20
23:31:17.682860 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.683018 IP 192.168.1.2.15000 > 121.7.133.118.55712: UDP, length 20
23:31:17.683066 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.683258 IP 192.168.1.2.15000 > 121.7.133.118.55712: UDP, length 20
23:31:17.683480 IP 192.168.1.2.15000 > 121.7.133.118.55712: UDP, length 20
23:31:17.689781 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.689992 IP 192.168.1.2.15000 > 121.7.133.118.55712: UDP, length 20
23:31:17.690046 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.690054 IP 121.7.133.118.55712 > 192.168.1.2.15000: UDP, length 1402
23:31:17.690444 IP 192.168.1.2.15000 > 121.7.133.118.55712: UDP, length 20
23:31:17.715350 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 0
23:31:17.737752 IP 78.235.238.208.57561 > 192.168.1.2.15000: tcp 1460
23:31:17.748112 IP 112.205.138.78.8999 > 192.168.1.2.15000: UDP, length 1470
23:31:17.748241 IP 112.205.138.78.8999 > 192.168.1.2.15000: UDP, length 1470
23:31:17.748322 IP 112.205.138.78.8999 > 192.168.1.2.15000: UDP, length 1470
23:31:17.748397 IP 192.168.1.2.15000 > 112.205.138.78.8999: UDP, length 20
23:31:17.748556 IP 192.168.1.2.15000 > 112.205.138.78.8999: UDP, length 20
23:31:17.775110 IP 173.239.240.69.14710 > 192.168.1.2.15000: UDP, length 1402
23:31:17.775368 IP 192.168.1.2.15000 > 173.239.240.69.14710: UDP, length 20
23:31:17.785800 IP 2.51.119.195.8999 > 192.168.1.2.15000: UDP, length 20
23:31:17.786186 IP 192.168.1.2.15000 > 78.235.238.208.57561: tcp 0
23:31:17.802766 IP 46.166.190.152.52165 > 192.168.1.2.15000: UDP, length 1462
23:31:17.802922 IP 46.166.190.152.52165 > 192.168.1.2.15000: UDP, length 1462
23:31:17.803014 IP 192.168.1.2.15000 > 46.166.190.152.52165: UDP, length 20
23:31:17.803086 IP 46.166.190.152.52165 > 192.168.1.2.15000: UDP, length 1462
23:31:17.803168 IP 192.168.1.2.15000 > 46.166.190.152.52165: UDP, length 20
23:31:17.803361 IP 192.168.1.2.15000 > 46.166.190.152.52165: UDP, length 20
23:31:17.803575 IP 2.51.119.195.8999 > 192.168.1.2.15000: UDP, length 1464
23:31:17.803774 IP 192.168.1.2.15000 > 2.51.119.195.8999: UDP, length 20
23:31:17.806133 IP 173.239.240.69.14710 > 192.168.1.2.15000: UDP, length 1402
23:31:17.806253 IP 192.168.1.2.15000 > 173.239.240.69.14710: UDP, length 20
23:31:17.817182 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 1452
23:31:17.817435 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 1452
23:31:17.817560 IP 192.168.1.2.15000 > 90.88.11.143.55378: tcp 0
23:31:17.817684 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 1452
23:31:17.818049 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 1452
23:31:17.818159 IP 192.168.1.2.15000 > 90.88.11.143.55378: tcp 0
23:31:17.818301 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 1452
23:31:17.818380 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 1452
23:31:17.818427 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 1452
23:31:17.818435 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 56
23:31:17.818566 IP 192.168.1.2.15000 > 90.88.11.143.55378: tcp 0
23:31:17.819680 IP 90.88.11.143.55378 > 192.168.1.2.15000: tcp 1452
4
Windows / Re: Outgoing port Min/Max
« Last post by Switeck on Today at 04:40:31 AM »
So trackers possibly/probably don't use the port range...good to know.

Does it at least partially work for peer/seed connections?
5
Windows / Re: Only Recieving Torrents Searches from 2 Plugins
« Last post by piso on Today at 02:50:37 AM »
I tried a more thorough uninstall using Revo uninstaller pro.  It did find a few persistent files which I deleted, but it didn't solve the problem.
6
Windows / Outgoing port Min/Max
« Last post by vg8open on Today at 02:49:36 AM »
Hello,

The outgoing port setting of qBittorrent doesn't seem to be working correctly.  I have the Outgoing ports (Min) = 50000 and Outgoing ports (Max) = 50010, but it doesn't seem to use that setting.  I captured the network traffic when it try to connect to a tracker with port 2710, and this this what it look like:

20:26:51.006434 IP 192.168.1.2.64970 > 91.210.106.252.2710: tcp 0
20:26:53.995750 IP 192.168.1.2.64970 > 91.210.106.252.2710: tcp 0

Clearly port 64970 is way out of range of port 50000...

Does any one know if there are any other settings I need to set to get it to work or is this a bug?

Thanks
7
Windows / Re: I had a PC crash since then...no speed and no seed
« Last post by Switeck on Today at 01:14:42 AM »
Zip up the temp folder, and also zip up qBT's settings folders.
Then if you damage/delete their contents you can recreate them from the zip files.
Hopefully, the temp folder doesn't contain 2+ GB of files.
8
Windows / Re: qBittorent won't close
« Last post by Ornlu on May 22, 2017, 10:16:43 PM »
I have the same issue. qbittorrent doesn't close manually. It will disappear from tray but I have to go to task manager and end process there.

I've tried (with no success):
- Clearing all finished torrents
- Emptying the torrent list completely
- Pausing torrents before I close
- Checking settings to determine if something interferes, couldn't figure out anything.
- Tried clean reinstall

This happens 100% of the time regardless of what I do. The only consistent way to shut down qbittorrent is to go to task manager and end the process. Otherwise, I'll just have to do it after trying to close it.

- If I go File->Exit still happens.
- If I X out (setting to close qbittorrent to tray turned off) still happens
- If I right-click on tray icon and click Exit still happens.
- If I try to shut down the computer without shutting down qbittorrent first (through end process) Windows will tell me that qbittorrent needs time to save before the computer can shut down. It remains in this state forever, meaning I have to manually tell Windows to override this.

I'm on Windows 7 64x Professional. I am using qbittorrent 3.3.12 (64-bit)
9
Windows / Re: I had a PC crash since then...no speed and no seed
« Last post by zpoison on May 22, 2017, 07:26:40 PM »
I am using version 3.3.4
Because after this version QBT is messing with the temp folder

after ver. 3.3.4 QBT has changed the way the save the temp files, all these numbers I don't like this at all

is this the same thing with the last version?

I have 2200 torrents, so when the temp folder is modified I fear that it will double the temp files by 2 or something (previous and new temp files)

I just don't like it, since also I KNOW that there is some errors in the temp folders sometimes (sometimes it does not delete the folder that you want to delete, or sometimes it does not MOVE the folder that is finished, for some reasons ,things like that)

---------------------------------------------------------

Switeck please, would you like to tell me how I could use the new version of QBT without risking to mess my temp folder, and that I would be able to revert back if I want to

a backup of the temp folder? I am confused about the step by step I should take , to not mess both versions temp folders
any idea?
10
Windows / Can't move or change filename after download complete
« Last post by chuccck on May 22, 2017, 07:05:33 PM »
After a file has reached 100%, has automatically stopped seeding per the ratio limits, and shows the status as "complete", qbittorrent won't let go of the file.  I get the error message "the action can't be completed because the file is open in qBitrroent - A Bittorrent Client".   I have auto downloads setup with sonarr and this happens 1 out every 5 downloads or so.  Any ideas?

Using version 3.3.1 on windows 7 64
Pages: [1] 2 3 ... 10