Increase web timeout for loading large shows #7271

Closed
opened 2026-02-07 04:47:06 +03:00 by OVERLORD · 5 comments
Owner

Originally created by @georgeh12 on GitHub (Aug 22, 2025).

I would like an easier way to increase the fetchWithFailover function timeout from 30 seconds.

The line from the "node_modules.jellyfin-apiclient.bundle.js" is: e.timeout = 3e4;

I am on the show page for south park that should display 27 seasons, and they fail to load. It looks like the code executes correctly, waits 30 seconds then triggers the timeout, then finishes loading the seasons in 45 seconds. It appears to try this twice, before giving up. Unfortunately, the jellyfin logs do not help, as this is a client-side issue.

The same thing happens on localhost, with a message from the server in the console logs: Request timed out to https://www.duckdns.org:8096/Shows/c9b83f57b950b2dc69a8e41081b10625/Seasons?userId=fca26e25ac5e48e6956a36ca448ec620&Fields=ItemCounts%2CPrimaryImageAspectRatio%2CCanDelete%2CMediaSourceCount

Running:

I added this section to my docker-compose to patch the issue:

    entrypoint:
      - /bin/bash
      - -c
      - |
        web_config_file="/jellyfin/jellyfin-web/node_modules.jellyfin-apiclient.bundle.js"
        echo '[WEB CONFIG] Starting background task to increase timeout of web requests from 30 seconds to 5 minutes...'
        # Start a background task to update the timeout
        (
            # optional; sleep 60
            if [ -f "$web_config_file" ]; then
                if grep -q 'e.timeout=3e4' "$web_config_file"; then
                    sed -i -E 's/e.timeout=3e4/e.timeout=3e5/g' "$web_config_file"
                    echo "[WEB CONFIG] Timeout successfully updated to 5 minutes: $web_config_file"
                else
                    echo "[WEB CONFIG] Timeout already updated to 5 minutes: $web_config_file"
                fi
            else
                echo "[WEB CONFIG] File not found: $web_config_file"
            fi
        ) &
        exec /jellyfin/jellyfin
Originally created by @georgeh12 on GitHub (Aug 22, 2025). I would like an easier way to increase the fetchWithFailover function timeout from 30 seconds. The line from the "node_modules.jellyfin-apiclient.bundle.js" is: `e.timeout = 3e4;` I am on the show page for south park that should display 27 seasons, and they fail to load. It looks like the code executes correctly, waits 30 seconds then triggers the timeout, then finishes loading the seasons in 45 seconds. It appears to try this twice, before giving up. Unfortunately, the jellyfin logs do not help, as this is a client-side issue. The same thing happens on localhost, with a message from the server in the console logs: Request timed out to https://www.duckdns.org:8096/Shows/c9b83f57b950b2dc69a8e41081b10625/Seasons?userId=fca26e25ac5e48e6956a36ca448ec620&Fields=ItemCounts%2CPrimaryImageAspectRatio%2CCanDelete%2CMediaSourceCount Running: - Jellyfin version 10.11.0-rc5 - Docker Desktop on Windows 11 - [jellyfin/jellyfin:preview 81ec9c521b42](https://hub.docker.com/layers/jellyfin/jellyfin/preview/images/sha256-81ec9c521b425bf7b1f6a67834729ba3e4923051156d1c909e9e1543272e6ffb) - Chrome 139 I added this section to my docker-compose to patch the issue: ``` entrypoint: - /bin/bash - -c - | web_config_file="/jellyfin/jellyfin-web/node_modules.jellyfin-apiclient.bundle.js" echo '[WEB CONFIG] Starting background task to increase timeout of web requests from 30 seconds to 5 minutes...' # Start a background task to update the timeout ( # optional; sleep 60 if [ -f "$web_config_file" ]; then if grep -q 'e.timeout=3e4' "$web_config_file"; then sed -i -E 's/e.timeout=3e4/e.timeout=3e5/g' "$web_config_file" echo "[WEB CONFIG] Timeout successfully updated to 5 minutes: $web_config_file" else echo "[WEB CONFIG] Timeout already updated to 5 minutes: $web_config_file" fi else echo "[WEB CONFIG] File not found: $web_config_file" fi ) & exec /jellyfin/jellyfin ```
Author
Owner

@sjorge commented on GitHub (Aug 22, 2025):

I don't think increasing the timeout is the right fix, this is probably a regression from 10.10.7 -> 10.11.0-rc.

Taking 45 seconds to load 27 seasons is way to long and almost nobody is going to wait for that.

Can you test on 10.10.7 to see if it also takes that long.

I suspect it won't take more than a second on 10.10.7, larges show i have is stargate with 10 seasons and it loads in about half a second fully rendered. Closer to 1 second with caching disabled.

Image
@sjorge commented on GitHub (Aug 22, 2025): I don't think increasing the timeout is the right fix, this is probably a regression from 10.10.7 -> 10.11.0-rc. Taking 45 seconds to load 27 seasons is way to long and almost nobody is going to wait for that. Can you test on 10.10.7 to see if it also takes that long. I suspect it won't take more than a second on 10.10.7, larges show i have is stargate with 10 seasons and it loads in about half a second fully rendered. Closer to 1 second with caching disabled. <img width="717" height="32" alt="Image" src="https://github.com/user-attachments/assets/3af156ea-a39d-4a4f-a979-07458fcb5aa6" />
Author
Owner

@georgeh12 commented on GitHub (Aug 22, 2025):

I migrated to 10.11 to avoid a killer bug with transcoding that wouldn't let me play certain shows. I never got to the bottom of it. Come to think of it, this same bug may have caused those shows to timeout during the transcode.
I'll rollback to that version and post logs later.

@georgeh12 commented on GitHub (Aug 22, 2025): I migrated to 10.11 to avoid a killer bug with transcoding that wouldn't let me play certain shows. I never got to the bottom of it. Come to think of it, this same bug may have caused those shows to timeout during the transcode. I'll rollback to that version and post logs later.
Author
Owner

@toytown2 commented on GitHub (Aug 23, 2025):

I have 27 seasons of south park on my server "10.10.7" and as you mentioned it takes less than a second to load.

@toytown2 commented on GitHub (Aug 23, 2025): I have 27 seasons of south park on my server "10.10.7" and as you mentioned it takes less than a second to load.
Author
Owner

@georgeh12 commented on GitHub (Aug 23, 2025):

Oh wow this is all true. I rolled back from 10.11 to 10.7 and things are running smoothly. I am going to enable trickplay and see if that was causing some of these issues.

@georgeh12 commented on GitHub (Aug 23, 2025): Oh wow this is all true. I rolled back from 10.11 to 10.7 and things are running smoothly. I am going to enable trickplay and see if that was causing some of these issues.
Author
Owner

@theguymadmax commented on GitHub (Dec 2, 2025):

Closing as a dupe of #14616

@theguymadmax commented on GitHub (Dec 2, 2025): Closing as a dupe of [#14616](https://github.com/jellyfin/jellyfin/issues/14616)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#7271