~25 requests to jellyfin every 5 minutes?

[Emporea]

Description

Pihole on the local network revealed about 25 dns queries to jellyfin every 5 minutes. I traced this back to jellyseerr. Why so many?

This results in ~ 7200 queries per day from jellyseerr alone.

Let me know if I can help with any logs.

Version

1.5.0

Steps to Reproduce

Setup docker container with jellyfin and jellyseer and connect them.
let it run.

Screenshots

Pi-hole data from several days. Jellyfin domain receives abnormal requests

Logs

No response

Platform

desktop

Device

/

Operating System

/

Browser

/

Additional Context

No response

Code of Conduct

• I agree to follow Overseerr's Code of Conduct

[fallenbagel]

Theres a jellyfin recently added sync job that runs every 5 minutes. That is why. If you want you can increase the cron timing of it to an hour to lessen the dns queries tho its just gonna leave you with a 1hm hour delay on syncing with jellyfin.

[fallenbagel]

I will be closing this issue as there are no follow ups. Feel free to reopen

[Emporea]

I followed your suggestion and changed it to an hour. The question still remains: why it has to access the url so often per cron job execution. Isnt it possible to access it only once per jellyfin sync job?

[michelsup]

I face the same issue, I get hundreds of thousands of DNS request per day, it's insane. I'm sure there should be a possibility to cache the answer for a few minutes.

[fallenbagel]

It's because of the way jellyfin user token works. You have to first call jellyfin, get the user access token, then call again using the access token to see if admin user before running library scan and stuff. If docker add the hosts with the ip so it resolves within the docker or filter out the jellyfin domain.

You can add this

image: ....
extra_hosts:
  - "jellyfin.url.com:172.16.0.5"   # "domain:ip"

If you're on native, you can add it to /etc/hosts or just filter out the domain on your dns resolver.

Until how user access tokens are fixed on jellyfins side (there was discussion on a way to improve this and plans for it), there's nothing we can really do when using access tokens.

[michelsup]

Thank you very much @fallenbagel , I didn't thought about setting the IP within docker. Well done.

[fallenbagel]

🎉 This issue has been resolved in version 1.9.1 🎉

The release is available on:

• v1.9.1
• GitHub release

Your semantic-release bot 📦🚀