2024-02-02, 03:58 AM
(This post was last modified: 2024-02-02, 04:09 AM by Efficient_Good_5784. Edited 4 times in total.)
Sorry, I now realize "192.168.1.1" is an optional gateway IP. I kind of forgot both "192.168.1.1" or "192.168.1.254" can be used as the gateway IP.
I didn't mean it like that. I'll edit that to be "192.168.1.#" just so that it makes sense with what it's supposed to be.
Just to note, this should be the same option as what is found in the Jellyfin dashboard under networking. Just scroll to the bottom and in the "Firewall and Proxy Settings" section, you will see the location of this option.
To be honest, my knowledge of this option is not great. I just included it because when I made my own compose file, I copied that over and never removed it just in case I ever needed it (just had it commented out so that it doesn't apply). It'll be better if you ask around and wait for someone with more knowledge about that option to explain it to you.
I did find this reddit post that will be useful here.
If you go to your dashboard and into the log section, at the very top you will see the option box to enable or disable this log warning.
You can also keep it enabled and choose a larger timeframe before your server sends this warning out if you find 500ms to be too fast to be considered a "slow response".
It sounds like your issue of Jellyfin being slow (on your Synology NAS I presume) is due to the scan. I would wait for the scan to complete. Unless you mess with your Synology NAS to install apps on an SSD, everything is running on the HDDs. With all the activity that a new library scan does, it would make sense that Jellyfin will be slow to load things to a client.
Now if you're wondering if your scan will never finish, you can then look at the logs to see if your Jellyfin server ran into some issue.
If you don't know how to read the logs, just make a thread here and paste them so others that do know what to look for can read it.
Just make sure to remove external IP addresses and other personal names and media path names.
I didn't mean it like that. I'll edit that to be "192.168.1.#" just so that it makes sense with what it's supposed to be.
Just to note, this should be the same option as what is found in the Jellyfin dashboard under networking. Just scroll to the bottom and in the "Firewall and Proxy Settings" section, you will see the location of this option.
To be honest, my knowledge of this option is not great. I just included it because when I made my own compose file, I copied that over and never removed it just in case I ever needed it (just had it commented out so that it doesn't apply). It'll be better if you ask around and wait for someone with more knowledge about that option to explain it to you.
I did find this reddit post that will be useful here.
(2024-02-02, 01:42 AM)denmalley Wrote: I have been trying to tackle the issue of "slow HTTP response"This is more of a useless log that the developers even put a "hush" option to make that log entry disappear from the logs.
If you go to your dashboard and into the log section, at the very top you will see the option box to enable or disable this log warning.
You can also keep it enabled and choose a larger timeframe before your server sends this warning out if you find 500ms to be too fast to be considered a "slow response".
It sounds like your issue of Jellyfin being slow (on your Synology NAS I presume) is due to the scan. I would wait for the scan to complete. Unless you mess with your Synology NAS to install apps on an SSD, everything is running on the HDDs. With all the activity that a new library scan does, it would make sense that Jellyfin will be slow to load things to a client.
Now if you're wondering if your scan will never finish, you can then look at the logs to see if your Jellyfin server ran into some issue.
If you don't know how to read the logs, just make a thread here and paste them so others that do know what to look for can read it.
Just make sure to remove external IP addresses and other personal names and media path names.