New Bug - v4.2.1 - All Trackers Listed as Error

[ryannathans]

Please provide the following information

qBittorrent version and Operating System

v4.2.1, Windows 10 1909

What is the problem

Since upgrading, on startup all torrents seem to be listed correctly but a small amount of time (I assume announcing to all trackers) all torrents/trackers appear as "Error" on the left category bar despite most torrents not having any errors on the trackers.

What is the expected behavior

As in previous versions, only torrents with tracker errors should appear listed under tracker "Errors"

Steps to reproduce

Start the program with existing torrents (that have trackers)

Extra info(if any)

Possibly related to having DHT, LSD and PEX disabled globally. (pls implement #7743 )

[ArcticGems]

Does qBittorrent's log show any errors? (if it does, post it)

[ryannathans]

No, the latest messages are binding to IP addresses

[ryannathans]

Maybe the trackers had errors but they show as working in this version?

I left the PC running for 2 hours and now only some show as "Error" (some of the errored ones have "not working" trackers, but some still show all "working")

[nokti]

Same here, I just upgraded to 4.2.1 and now all my torrents but one are showing tracker error. 90% of my torrents are private, with DHT disabled and only one tracker annonce per torrent which says working.

[ryannathans]

Another few hours and they're all back to error again. No idea why but it's definitely some new bug in 4.2.1. Same situation as @nokti with 90% private trackers, no DHT/PEX/LSD and 1-3 trackers per torrent that say working (and none that say not working)

[p43b1]

Confirm. Windows 10 4.2.1 all tackers not working

[Desiato66]

Came here looking for an answer to this problem so I have registered to confirm this bug. I have two private trackers, one seeding 41 torrents and 95% are working but in the Error section. The other tracker with 312 seeds with roughly half Not Working and half Working. Force reannouncing them removes them from the Error section but within an hour they are all back in the Error section again.

[ghost]

The trackers are working fine but qBit is moving them to error section.

[Desiato66]

Yeah, I should have said the larger tracker is having issues so the Not Working is not the fault of qBittorrent.

[beeeeswax]

Same problem here, torrents bounce in and out of the 'Error' section of the Trackers node. None of them show anything in the 'Message' column and their status is always 'Working'. Tracker site shows all torrents seeding also so it appears to be a cosmetic issue. No errors in the qBit execution log.

qBit 4.2.1
Windows Server 2019 (fully patched)

[Lash78]

This bug is related to ipv6. Workaround: change bind ip in advanced options to "All IPv4 addresses".

[Desiato66]

@Lash78 The All IPv4 addresses setting has fixed the issue with one tracker (which is struggling to maintain connection for its torrents so they keeping appearing in the Error section as Not Working but after a reboot today, I have 6 working torrents from another tracker in the Error section so not completely fixed.

[ArcticGems]

This bug is related to ipv6. Workaround: change bind ip in advanced options to "All IPv4 addresses".

@Lash78 The All IPv4 addresses setting has fixed the issue with one tracker (which is struggling to maintain connection for its torrents so they keeping appearing in the Error section as Not Working but after a reboot today, I have 6 working torrents from another tracker in the Error section so not completely fixed.

@sledgehammer999 @Chocobo1
Did this bug get introduced by PR = #11592 ?

[sledgehammer999]

Can you guys try this test build? It PR #11733 on top of 4.2.1.
Remember to re-enable all interfaces/all addresses.
Link: http://builds.shiki.hu/temp/qbittorrent_4.2.1_x64_patched_for_issue_11691.7z

(run it from any folder or overwrite original files)

[Lash78]

Almost good... but when you start the program, it shows the errors first and then starts to decreasing to zero.

[sledgehammer999]

Almost good... but when you start the program, it shows the errors first and then starts to decreasing to zero.

I think that's inevitable and probably ok. The first endpoints to "report back" are probably the dummy local IPv6 addresses which will report a failure. But as soon as the IPv4 addresses contacts the tracker (which is a slower operation than locally fail) the errors will be zeroed out per torrent per tracker.

[ghost]

Can you guys try this test build? It PR #11733 on top of 4.2.1.
Remember to re-enable all interfaces/all addresses.
Link: http://builds.shiki.hu/temp/qbittorrent_4.2.1_x64_patched_for_issue_11691.7z

(run it from any folder or overwrite original files)

It's working as expected.

[beep054]

This bug is related to ipv6. Workaround: change bind ip in advanced options to "All IPv4 addresses".
This doesn't seem to work at all.

[influx3k]

Still having this issue with 4.2.4. All torrents errored but one. All the ones that are errored say "Not Working" but no tracker message. Did see this error in the Execution Log:

4/24/20 9:34 PM - Failed to listen on IP: 192.168.1.11, port: UDP/32500. Reason: Address already in use

[FranciscoPombal]

4/24/20 9:34 PM - Failed to listen on IP: 192.168.1.11, port: UDP/32500. Reason: Address already in use

There is a program running already bound to that endpoint. Terminate that program or configure it to use another address/port, and restart qBittorrent.