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
xbytes not working well #15239
Comments
None of the active maintainers have an account, so you're going to need to be more descriptive than 'not working well'. Feel free to use Google Translate or DeepL.com if English isn't your first language. Please provide the actual version number of Jackett (available at the bottom of the webUI), as 'latest' is meaningless, especially when dealing with Docker. If you have an invite, please send it to If not, please provide and enhanced log of a test search with xbytes - https://github.com/Jackett/Jackett/wiki/Troubleshooting#how-to-provide-a-jackett-enhanced-log-for-a-ticket |
Based on your post on the Prowlarr repo (Prowlarr/Indexers#436), the issue is that irrelevant results are being returned. From the logs it appears that you've enabled searching for freeleech torrents only. Try disabling that and see if it resolves the issue. If not, you can try searching for If not, post an enhanced log (link above) and the URL of that search on the site in browser. |
Ok, basically the problem is the same, right now jackett and prowlarr are not able to detect that xbytes torrents are freelech correctly. As soon as you disable it results appear (same in both). I think it's because in the xbytes torrent page it doesn't appear if it's freelech, only in the search results section. Right now Xbytes has global Free Leech until Friday 10th May 2024 at 8:00 pm By the way I tried to make the blog but for some reason in my docker in the path /data/Jackett/Logs the file was last modified on 08/04/2024, I don't know why it is not updating, I was going to delete it to see if it was created again. |
IF you have already looked at the web sites torrents search page, and if on each of the torrent rows there is no freeleech flag of any kind, then there is nothing the indexer can use to indicate a freeleech in its processed results. I will raise an enhancement ticket to see if we can implement global freeleech detection, because this is a common issue across many sites running different engines, and I believe it should be possible to support this with cardigann. Closing this ticket. |
fallout-example.txt Right now xbytes has freelech on the site, just the indexer is not able to detect the tags, that was the error. I am sending you the html so you can update the tags with 2 tests that I have done and that the indexer does not reflect that they have freelech. Thanks |
Yes, I see that the indexer is out of date, only looking for gold, silver and bronze flags. |
Given its free text this may not be consistently the same text every global freeleech event, but as long as we get notified we can update for the next one.
@garfield69 can you take a look at Prowlarr/Indexers#436 (comment) if you have an account? |
I know what the error is. In your URL it makes me search with a web selector called "Search in" and with the filter "Selected gold torrents". When I activate that search filter it shows random results. If you activate Search in "Gold torrents, Silver torrents, Bronze torrents" it has stopped working well on the web. The search works fine with the first option "Filename" ("Nombre del archivo"in spanish) by default which I think is how it works without checking freelech in your developments. Attached is a search without using the "Golf torrents" filter that gives results for freelech torrents as well. I attach a search without using the "Golf torrents" filter which gives results for freelech torrents as well. |
OK. I think i understand what you are saying. |
yes, that is exactly what happens, it would be to use the search engine in its version without freelech search that you currently have but in the results eliminate all those that do not have the gold gif. |
v0.21.2387 |
Xbytes admins might have blocked on purpose the use of Jackett or Prowlarr, or at least it's what I've read in some telegram groups about spanish trackers. |
Have you checked our Troubleshooting page for your issue?
Is there already an issue for your problem?
Have you read our Contributing Guidelines?
Environment
Description
I am using the latest version of Jackett in Docker and I have noticed from the beginning that xbytes is not offering the results well, this error is also occurring with prowlarr, I think it is due to the current website or similar
Logged Error Messages
Screenshots
No response
The text was updated successfully, but these errors were encountered: