Ahoy!
I’m a veteran pirate and pretty familiar with the standard *arr stack of resources, but recently decided to run Whisparr.
I also signed up for a new private tracker and got it setup through Jackett and confirmed working in jackett. The problem is, when I manually search for a release in Whisparr it comes back with no results, but searching the same release from jackett (or the tracker directly) I see the release is available.
I think I might know what’s going on. I think the tracker has releases dated day/mo/yr and Whisparr is looking for mo/day/yr. This is totally a guess, but it’s all I’ve found so far that might be causing the issue. Was wonder if anyone had a similar issue or a potential resolution.
Thanks in advance!
EDIT: So, I think the issue is the date. Looking at the logs Whisparr searches for “release+yr.mo.d” and the tracker has releases listed with “release+d.mo.yr”. I confirmed this by trying the search Whisparr was running manually through Jackett. I guess I’ll have to see if I can add additional search terms or something or find a different tracker. I’ll update with a solution if I find one
I haven’t used whisparr, but have you checked the logs, or this is just a hunch?
My theory is just a hunch, the logs don’t give any info except that 0 releases were found
Have you turned on debug logs? I haven’t used Whisparr, but on the other *arrs, debug logging gives more information about how they searched, and if something was found but rejected.
Yup, Debug doesn’t give much more info. Appreciate the help though!
Ah, that’s a shame. Good luck :)
My theory is just a hunch, the logs don’t give any info except that 0 releases were found
If it’s indeed an issue then you may want to submit it in their Github so that it could be fixed in the future?
https://github.com/Whisparr/Whisparr/issues
Interestingly someone did submit something similar a while back, but for some reason the submitter closed their own issue without any code being submitted to resolve it. Unclear what happened there or if it’s related to your issue https://github.com/Whisparr/Whisparr/issues/58
I don’t know if I’d consider this a issue with Whisparr or with the tracker. All the trackers I’ve used in the past use UTC standards on date format for releases. I think this new trackers standard is just different for some reason and that breaks Whisparr. Maybe I could put in a feature request to allow the date format to be changed in the query.
I don’t know if I’d consider this a issue with Whisparr or with the tracker.
Maybe a bit of both, you could reach out to both of them I guess. But overall I’d think the onus is on Whisparr devs to work towards being compatible with any indexer thrown their way. It is unlikely that any tracker admins will prioritize being compatible with Whisparr so tracker admins may not see it as an issue worth fixing on there end.
EDIT: Not sure if you can see this reply since Lemmy.world just started blocking piracy related communities (see https://lemmy.world/post/3175920), may be worth creating an account here or another Lemmy instance that isn’t blocking [email protected]
Are you running these in docker? If so read on otherwise this probably won’t help you.
I encountered a similar problem with my Sonarr/Radarr setup and Prolwarr indexer. I would have no results in sonarr/radarr but would have results when searching directly in prowlarr. Ultimately I discovered it was a dns issue.
I had a custom domain setup to access my sonarr/radarr services (eg., sonarr[.]mydomain[.]com). When I’d search through either sonarr or radarr the program would ping Prowlarr, but prowlarr would send the results back to the internal docker ip and not through to my custom domain. So I was seeing no results. My solution was to just access sonarr/radarr with their designated ips and ports rather than my custom domain.
Hope you are able to figure it out.
Not in Docker, running on an Ubuntu VM. I’m using IP addresses for everything. I should add, it works fine with Jackett using a different tracker.
