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

[Bug Report] [Failure reason \"This client is not allowed...] #1267

Open
Suitear opened this issue Mar 14, 2024 · 3 comments
Open

[Bug Report] [Failure reason \"This client is not allowed...] #1267

Suitear opened this issue Mar 14, 2024 · 3 comments

Comments

@Suitear
Copy link

Suitear commented Mar 14, 2024

OS: Debian 11/10, Ubuntu 20.04
Client: rtorrent 0.9.8/libtorrent 0.13.8

On several trackers, the tracker would occasionally give feedback like:
`Tracker: [Failure reason "This client is not allowed. Please goto xxxx.com/faq.php#id29 for a list of acceptable clients"]'

I install rtorrent0.9.8/libtorrent0.13.8 via source compilation at first. And after I found this issue, I reinstall rtorrent via apt way.
But it didn't solve this problem in either way. By the way, rtorrent is on client whitelist of those trackers.
So I asked reletive staff on those trackers for help. Their reply is as follows.

The high probability is the http/2 bug of libcurl, which the new version of transmission has fixed, but rTorrent has not been maintained for a long time. The bug will cause random data-reports to be lost (As for client, it will appear as an illegal client).

Solution: rTorrent has not updated to fix this bug. Therefore, if you want to solve the problem, you can only change QBittorrent/Transmission. Or live with it`

So please look into this. Thanks.

@kannibalox
Copy link
Contributor

kannibalox commented Mar 14, 2024

If this is the bug in question: transmission/transmission#1563, then just like with transmission, the fix needs to come from an updated version of curl. Following the ticket trail, it looks like the earliest version with the fix is 7.75.0, or you can try downgrading curl to a previous version. Unfortunately it doesn't look like there's anything that can be changed in rTorrent to fix this.

Edit: it looks like it was introduced in version 7.71.0, so anything between that and 7.75.0 would be effected

@Suitear
Copy link
Author

Suitear commented Mar 15, 2024

Thanks. So if I upgrade curl to 7.75+ independently, it would be solved?

@kannibalox
Copy link
Contributor

As long as rtorrent is linked against 7.75+, I would expect things to work correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants