Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54476 readers

274 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others

Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):

💰 Please help cover server costs.


Ko-fi	Liberapay

founded 1 year ago

MODERATORS

db0@lemmy.dbzer0.com

sunbrothersco@lemmy.dbzer0.com

dataprolet@lemmy.dbzer0.com

Flatworm7591@lemmy.dbzer0.com

RandomLegend@lemmy.dbzer0.com

Help getting Whisparr to work with private tracker (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by ZeroCooler@lemmy.world to c/piracy@lemmy.dbzer0.com

12 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] coffeeguy@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] ZeroCooler@lemmy.world 2 points 1 year ago

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.