![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://lemmy.dbzer0.com/pictrs/image/a18b0c69-23c9-4b2a-b8e0-3aca0172390d.png)
Yup, Debug doesn’t give much more info. Appreciate the help though!
Yup, Debug doesn’t give much more info. Appreciate the help though!
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
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.
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.