Hi,
First, thank you all for working on qBittorrent, Everything I've seen so far about the program I like and I've been able to get great speeds with just the small amount of peers I can connect to.
The problem I'm having is that on all my torrents (using several different trackers) the UDP trackers will show working but the HTTP trackers will be stuck on Not Working. I can download/upload on torrents with UDP trackers fine, but any torrents I have with HTTP trackers don't work. However, when I try to use any other bittorrent software both UDP and HTTP trackers work fine. I've tried performing a clean install, rebooting my computer, using UPnP port forwarding, manual port forwarding, disabling/enabling UTP, disabling/enabling DHT, disabling/enabling PEX and so far nothing works. Canyouseeme.org shows me as connectable on port 6881, the port I'm using for qBittorrent.
I'm running qBittorrent 3.1.5 on Windows 7 64-bit. Here's my execution log:
18/01/2014 02:18:11 - External IP: xxx.xxx.xxx.xxx
18/01/2014 02:18:11 - qBittorrent is successfully listening on interface :: port: TCP/6881
18/01/2014 02:18:11 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/6881
18/01/2014 02:18:08 - Options were saved successfully.
18/01/2014 02:18:08 - Embedded Tracker [OFF]
18/01/2014 02:18:08 - Encryption support [ON]
18/01/2014 02:18:08 - Local Peer Discovery support [ON]
18/01/2014 02:18:08 - PeX support [ON]
18/01/2014 02:18:08 - DHT support [ON], port: UDP/6881
18/01/2014 02:18:08 - Anonymous mode [OFF]
18/01/2014 02:18:08 - HTTP user agent is qBittorrent v3.1.5
18/01/2014 02:18:08 - UPnP / NAT-PMP support [ON]
18/01/2014 02:18:08 - qBittorrent is trying to listen on any interface port: TCP/6881
18/01/2014 02:18:08 - Peer ID: -qB3150-
Thank you very much for any help, and let me know if you need any more information.
UDP trackers working, but HTTP trackers not working
Re: UDP trackers working, but HTTP trackers not working
Try using a port other than 6881, as 6881 - 6999 are the 'well known' ports used byBitTorrent clients so your ISP may be blocking 6881 for TCP
Re: UDP trackers working, but HTTP trackers not working
True, it would be better if the ports that qBittorrent is using should be random instead 6881. Mine is using 20000 for example.
Re: UDP trackers working, but HTTP trackers not working
A port within the 49152 - 65534 range is suggested as this will avoid Internet Service Provider (ISP) blocks and possible conflicts with other programs.
Re: UDP trackers working, but HTTP trackers not working
Did you say that you ENABLED announce to multiple trackers? Because, just in case you didn't know, by default qB only "needs" to connect to one tracker at a time and lately it's very likely that UDP trackers are listed first.
Re: UDP trackers working, but HTTP trackers not working
Thanks for the help, everyone. I tried several other ports both within the 49152 - 65534 range and outside of it, but no change. Loki, I did enable announce to all trackers, but still the same situation. I've also tried changing the network interface to all of the available options.
EDIT:
I noticed that when I start qBittorrent, several minutes after it starts, this message shows up in the execution log:
18/01/2014 20:01:02 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP: no router found
18/01/2014 20:01:02 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP: no router found
18/01/2014 20:01:02 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP: no router found
I'm puzzled by this because even if the UPnP port mapping fails, shouldn't manual port forwarding solve the problem (which I tried to no avail)?
EDIT:
I noticed that when I start qBittorrent, several minutes after it starts, this message shows up in the execution log:
18/01/2014 20:01:02 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP: no router found
18/01/2014 20:01:02 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP: no router found
18/01/2014 20:01:02 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP: no router found
I'm puzzled by this because even if the UPnP port mapping fails, shouldn't manual port forwarding solve the problem (which I tried to no avail)?
Last edited by tvonradio on Sun Jan 19, 2014 1:04 am, edited 1 time in total.
Re: UDP trackers working, but HTTP trackers not working
Indicates that there is no local router that supports UPnP.could not map port using UPnP: no router found
Are you using a "Cable Modem" with a single ethernet port?