• 1 Post
  • 7 Comments
Joined 1Y ago
cake
Cake day: Jul 02, 2023

help-circle
rss

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.



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.


My theory is just a hunch, the logs don’t give any info except that 0 releases were found


My theory is just a hunch, the logs don’t give any info except that 0 releases were found


Help getting Whisparr to work with private tracker
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
fedilink

This is basically my setup.

My NAS has individual folders for torrent files, downloads in progress, Seeding.

Radarr/Sonarr monitors the Seeding folder. Then copies the file to the appropriate folder for Plex.


This really depends on the services you’re paying for from the colo.

Assuming they offer internet services, you can probably chooses between a static or dynamic IP for your WAN IP. For your internal network, you would be responsible for DHCP or static assignment.

You’ll also need a security device like a firewall or router that can perform NAT for your internal addresses.

This info is assuming a lot, I’m not sure if you’re paying for a service that might include the WAN networking component, or if you’re just paying for power and real estate.

Happy to help with any more info if you have specific questions.

Also, you should be able to physically access your gear yourself so you’re not paying for smart hands. I would ask the colo of their access hours are anything other than 24/7.