Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All Trackers 'Not Working', #2683

Closed
MattJunks opened this issue Mar 9, 2015 · 14 comments
Closed

All Trackers 'Not Working', #2683

MattJunks opened this issue Mar 9, 2015 · 14 comments

Comments

@MattJunks
Copy link

OS: Windows 7
Version: qBittorrent v3.1.1.12
Windows Firewall allowed for Public and Private locations.
Always announce to all trackers enabled.
Uninstalled, reinstalled, exited, reopened.
Port is forwarded.
Not working for five different private trackers, all of which allow the latest version of qBittorent in their Rules.
Same torrents and trackers worked in uTorrent. Moved over and found that I could download for a little bit, but not upload at all. After latest reinstall I can no later download as well.
The tracker also has not supplied a message other than 'Not Working'.

image

@git-project-one
Copy link

I'm running Mac OSX and running into this same issue. Everything will be running along then get into this state.

The only way I've seen to get out of it is to dump my preferences.

@shebang4
Copy link

I had the same issue, unchecking the "Listening to IPv6 addresses" box in the options->advanced tab solved it.

@git-project-one
Copy link

Hmm, I checked that setting and mine was unchecked. So I checked it and it started working. I feel qBittorrent could use some improvement in detecting these issues and working around them dynamically.

@shebang4
Copy link

Interesting, do you actually have an IPv6 address by yourself?

@git-project-one
Copy link

My router hands out ipv6 however not enabled ISP side. I guess a simple enough solution is to disable ipv6 on the router. However that is a workaround to the root problem which is qBittorrent binding to the wrong IP.

@MattJunks
Copy link
Author

Solved it on my end;

When you scroll in the settings tabs, sometimes the dropdowns on the tab scroll with it. This caused me to accidentally add a blank proxy server (0.0.0.0), which then cut out my connection. Didn't realize it until I went one by one through my settings.

So, to add an additional thing to check onto this issue, make sure you do not have a blank proxy server enabled. Once I removed that my issue was solved.

@ngosang
Copy link
Member

ngosang commented Jun 24, 2015

@sledgehammer999 close. Looks like this is a forum question not a bug.

@ghost
Copy link

ghost commented Dec 20, 2016

@MattJunks Your answer helped me almost a year and a half later, thanks for sharing the solution. I did the same thing, I scrolled on the proxy dropdown and changed it from none to socks4 0.0.0.0

I would have never figured this out without your post.. I didn't know I changed anything

@tacologic
Copy link

tacologic commented Jun 18, 2017

Had this problem as well. Above fixes didn't work. Enabling anon mode did.

EDIT: This is not correct, just a coincidence. Actual problem seems to be that some of the IPs that I'm grabbing don't connect.

@stressedredneck
Copy link

Another quick fix that I found after having this same issue was to check the port used for incoming connections under "Options", "Connections". Mine was set by default to something besides 6881. Once I changed it to this, it started working again.

@nocibambi
Copy link

Solved it on my end;

When you scroll in the settings tabs, sometimes the dropdowns on the tab scroll with it. This caused me to accidentally add a blank proxy server (0.0.0.0), which then cut out my connection. Didn't realize it until I went one by one through my settings.

So, to add an additional thing to check onto this issue, make sure you do not have a blank proxy server enabled. Once I removed that my issue was solved.

I just had the exact same issue...three and a half year later... :-O

@Horrgakx
Copy link

Horrgakx commented Jan 27, 2019

I've just had this issue for a week and a couple of my friends have looked at it too. I've even signed up to a new VPN service which allows port forwarding. Nothing would work with qBittorrent, and I even tried the current and an old version. I also tried turning the Win10 firewall completely off. Nothing worked.

I switched back to uTorrent and it's seeding now. Very odd.

@JonasNilson
Copy link

My issue was caused by the "Network Interface" being set to something that wasn't working properly (I changed it back to 'Any interface' as a quick solution):
image

@afgks
Copy link

afgks commented Jan 25, 2020

My issue was caused by the "Network Interface" being set to something that wasn't working properly (I changed it back to 'Any interface' as a quick solution):
image

Thank you, you solved my problem!

@qbittorrent qbittorrent locked and limited conversation to collaborators Feb 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests