jellyseerr icon indicating copy to clipboard operation
jellyseerr copied to clipboard
verified publisher icon Fallenbagel

Server crashing while browsing the UI

Open jstewart3802 opened this issue 11 months ago • 21 comments

Description

The server sometimes when using the UI seems to crash with no logs, running in TrueNAS.

This happens whenever doing anything from what I can tell, including searching for a show or movie, or adding something to watch list, or clicking on any show or movie to get more info on it. Although it doesn't happen every time, but I can't see a theme as to what causes it.

If there is any other info I can prodicde that would be halpful I can gather anything required.

Version

2.2.3

Steps to Reproduce

  1. Start Server
  2. Open ui and do anything (Search for show/movie, browse recomended)
  3. Server crashes with no info

Screenshots

No response

Logs

2025-01-13 16:50:35.914192+00:00> [email protected] start /app
2025-01-13 16:50:35.914205+00:00> NODE_ENV=production node dist/index.js
2025-01-13 16:50:35.914217+00:002025-01-13T16:50:35.914217146Z
2025-01-13 16:50:38.341407+00:002025-01-13T16:50:38.338Z [[32minfo[39m]: Commit Tag: $GIT_SHA 
2025-01-13 16:50:39.425917+00:002025-01-13T16:50:39.425Z [[32minfo[39m]: Starting Overseerr version 2.2.3 
2025-01-13 16:50:40.335799+00:002025-01-13T16:50:40.335Z [[34mdebug[39m][Settings Migrator]: Checking migration '0001_migrate_hostname.js'... 
2025-01-13 16:50:40.338344+00:002025-01-13T16:50:40.338Z [[34mdebug[39m][Settings Migrator]: Checking migration '0002_migrate_apitokens.js'... 
2025-01-13 16:50:40.340154+00:002025-01-13T16:50:40.339Z [[34mdebug[39m][Settings Migrator]: Checking migration '0003_emby_media_server_type.js'... 
2025-01-13 16:50:40.341546+00:002025-01-13T16:50:40.341Z [[34mdebug[39m][Settings Migrator]: Checking migration '0004_migrate_region_setting.js'... 
2025-01-13 16:50:40.363620+00:002025-01-13T16:50:40.363Z [[32minfo[39m][Notifications]: Registered notification agents 
2025-01-13 16:50:40.423305+00:002025-01-13T16:50:40.423Z [[32minfo[39m][Jobs]: Scheduled jobs loaded 
2025-01-13 16:50:40.699354+00:002025-01-13T16:50:40.698Z [[32minfo[39m][Server]: Server ready on port 30042 
2025-01-13 16:51:00.014078+00:002025-01-13T16:51:00.013Z [[34mdebug[39m][Jobs]: Starting scheduled job: Download Sync 
2025-01-13 16:52:00.051917+00:002025-01-13T16:52:00.051917685Z
2025-01-13 16:52:00.052161+00:00> [email protected] start /app
2025-01-13 16:52:00.052175+00:00> NODE_ENV=production node dist/index.js
2025-01-13 16:52:00.052184+00:002025-01-13T16:52:00.052184687Z
2025-01-13 16:52:02.547410+00:002025-01-13T16:52:02.545Z [[32minfo[39m]: Commit Tag: $GIT_SHA 
2025-01-13 16:52:03.687626+00:002025-01-13T16:52:03.687Z [[32minfo[39m]: Starting Overseerr version 2.2.3 
2025-01-13 16:52:04.669469+00:002025-01-13T16:52:04.668Z [[34mdebug[39m][Settings Migrator]: Checking migration '0001_migrate_hostname.js'... 
2025-01-13 16:52:04.672212+00:002025-01-13T16:52:04.671Z [[34mdebug[39m][Settings Migrator]: Checking migration '0002_migrate_apitokens.js'... 
2025-01-13 16:52:04.674148+00:002025-01-13T16:52:04.673Z [[34mdebug[39m][Settings Migrator]: Checking migration '0003_emby_media_server_type.js'... 
2025-01-13 16:52:04.675667+00:002025-01-13T16:52:04.675Z [[34mdebug[39m][Settings Migrator]: Checking migration '0004_migrate_region_setting.js'... 
2025-01-13 16:52:04.682370+00:002025-01-13T16:52:04.681Z [[32minfo[39m][Notifications]: Registered notification agents 
2025-01-13 16:52:04.759246+00:002025-01-13T16:52:04.758Z [[32minfo[39m][Jobs]: Scheduled jobs loaded 
2025-01-13 16:52:05.047822+00:002025-01-13T16:52:05.047Z [[32minfo[39m][Server]: Server ready on port 30042 
2025-01-13 16:53:00.013894+00:002025-01-13T16:53:00.013Z [[34mdebug[39m][Jobs]: Starting scheduled job: Download Sync 
2025-01-13 16:54:00.009629+00:002025-01-13T16:54:00.009Z [[34mdebug[39m][Jobs]: Starting scheduled job: Download Sync 
2025-01-13 16:55:00.040694+00:002025-01-13T16:55:00.040Z [[34mdebug[39m][Jobs]: Starting scheduled job: Download Sync 
2025-01-13 16:55:00.062392+00:002025-01-13T16:55:00.060Z [[32minfo[39m][Jobs]: Starting scheduled job: Jellyfin Recently Added Scan 
2025-01-13 16:55:00.066235+00:002025-01-13T16:55:00.064Z [[32minfo[39m][Jellyfin Sync]: Jellyfin Sync Starting {"sessionId":"3847b9b3-944a-4c08-aa61-235f58e21343"}
2025-01-13 16:55:00.087498+00:002025-01-13T16:55:00.086Z [[32minfo[39m][Jellyfin Sync]: Beginning to process recently added for library: Movies 
2025-01-13 16:55:00.571795+00:002025-01-13T16:55:00.571Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Red One 
2025-01-13 16:55:00.603206+00:002025-01-13T16:55:00.602Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Heretic 
2025-01-13 16:55:00.647502+00:002025-01-13T16:55:00.647Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Patient Zero 
2025-01-13 16:55:00.666955+00:002025-01-13T16:55:00.666Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Dear Santa 
2025-01-13 16:55:00.683612+00:002025-01-13T16:55:00.683Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found The Hunger Games: Catching Fire 
2025-01-13 16:55:00.698270+00:002025-01-13T16:55:00.698Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Blade 
2025-01-13 16:55:00.731783+00:002025-01-13T16:55:00.731Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Operation Finale 
2025-01-13 16:55:00.765671+00:002025-01-13T16:55:00.765Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Conspiracy 
2025-01-13 16:55:00.775825+00:002025-01-13T16:55:00.773Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Longlegs 
2025-01-13 16:55:00.804369+00:002025-01-13T16:55:00.804Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Memoir of a Snail 
2025-01-13 16:55:00.810308+00:002025-01-13T16:55:00.810Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found Elevation 
2025-01-13 16:55:00.812463+00:002025-01-13T16:55:00.812Z [[34mdebug[39m][Jellyfin Sync]: Title already exists and no new media types found The Blackcoat's Daughter 
2025-01-13 16:55:04.819309+00:002025-01-13T16:55:04.817Z [[32minfo[39m][Jellyfin Sync]: Beginning to process recently added for library: Shows 
2025-01-13 16:55:05.077805+00:002025-01-13T16:55:05.077Z [[34mdebug[39m][Jellyfin Sync]: Updating existing title: Star Wars: Skeleton Crew 
2025-01-13 16:55:05.153313+00:002025-01-13T16:55:05.152Z [[34mdebug[39m][Jellyfin Sync]: Updating existing title: Dune: Prophecy 
2025-01-13 16:55:05.224023+00:002025-01-13T16:55:05.223Z [[34mdebug[39m][Jellyfin Sync]: Updating existing title: Boston Legal 
2025-01-13 16:55:05.346360+00:002025-01-13T16:55:05.346Z [[34mdebug[39m][Jellyfin Sync]: Updating existing title: Shrinking 
2025-01-13 16:55:05.378853+00:002025-01-13T16:55:05.378Z [[34mdebug[39m][Jellyfin Sync]: Updating existing title: Silo 
2025-01-13 16:55:05.454269+00:002025-01-13T16:55:05.454Z [[34mdebug[39m][Jellyfin Sync]: Updating existing title: Slow Horses 
2025-01-13 16:55:05.457277+00:002025-01-13T16:55:05.457Z [[34mdebug[39m][Jellyfin Sync]: Updating existing title: Attack on Titan 
2025-01-13 16:55:09.457584+00:002025-01-13T16:55:09.457Z [[32minfo[39m][Jellyfin Sync]: Recently Added Scan Complete 
2025-01-13 16:55:49.145745+00:002025-01-13T16:55:49.145745719Z
2025-01-13 16:55:49.145889+00:00> [email protected] start /app
2025-01-13 16:55:49.145901+00:00> NODE_ENV=production node dist/index.js
2025-01-13 16:55:49.145910+00:002025-01-13T16:55:49.145910622Z
2025-01-13 16:55:55.527975+00:002025-01-13T16:55:55.513Z [[32minfo[39m]: Commit Tag: $GIT_SHA 
2025-01-13 16:55:57.917906+00:002025-01-13T16:55:57.917Z [[32minfo[39m]: Starting Overseerr version 2.2.3 
2025-01-13 16:56:00.227448+00:002025-01-13T16:56:00.226Z [[34mdebug[39m][Settings Migrator]: Checking migration '0001_migrate_hostname.js'... 
2025-01-13 16:56:00.236526+00:002025-01-13T16:56:00.236Z [[34mdebug[39m][Settings Migrator]: Checking migration '0002_migrate_apitokens.js'... 
2025-01-13 16:56:00.245899+00:002025-01-13T16:56:00.245Z [[34mdebug[39m][Settings Migrator]: Checking migration '0003_emby_media_server_type.js'... 
2025-01-13 16:56:00.251455+00:002025-01-13T16:56:00.251Z [[34mdebug[39m][Settings Migrator]: Checking migration '0004_migrate_region_setting.js'... 
2025-01-13 16:56:00.279882+00:002025-01-13T16:56:00.279Z [[32minfo[39m][Notifications]: Registered notification agents 
2025-01-13 16:56:00.482778+00:002025-01-13T16:56:00.482Z [[32minfo[39m][Jobs]: Scheduled jobs loaded 
2025-01-13 16:56:00.888322+00:002025-01-13T16:56:00.887Z [[32minfo[39m][Server]: Server ready on port 30042 
2025-01-13 16:57:00.019876+00:002025-01-13T16:57:00.019Z [[34mdebug[39m][Jobs]: Starting scheduled job: Download Sync

Platform

desktop

Database

None

Device

Windows PC

Operating System

Windows 11

Browser

Chrome

Additional Context

No response

Code of Conduct

  • [X] I agree to follow Jellyseerr's Code of Conduct

jstewart3802 avatar Jan 13 '25 17:01 jstewart3802

If trunas uses docker i would check the docker logs. If there are no logs on jellyseerr it sounds like it's not jellyseerr but the container crashing

fallenbagel avatar Jan 13 '25 17:01 fallenbagel

I am experiencing the same issue. @Fallenbagel your comment caused me to look at the docker logs and it seems like when internal jobs are running it is timing out because it can't reach itself on the configured localhost:30042. The port 30042 is pre-configured as the host port, when using the community app in TrueNAS. I am going to install Jellyseer now using docker compose in TrueNAS, keeping the default port mapping of 5055:5055 and see if that resolves the issue.

EDIT: Issue remains. Here the docker logs

2025-01-15T15:09:11.029Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch discover TV: fetch failed"} 2025-01-15T15:09:11.034Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: fetch failed"} 2025-01-15T15:09:11.035Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch discover movies: fetch failed"} ⨯ TypeError: fetch failed at node:internal/deps/undici/undici:13392:13 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async M.getInitialProps (/app/.next/server/chunks/51084.js:5:34051) at async X (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5045) at async e3 (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:25:3773) at async doRender (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1425:30) at async cacheEntry.responseCache.get.routeKind (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1599:28) at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1507:28) at async NextNodeServer.renderPageComponent (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1931:24) at async NextNodeServer.renderToResponseImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1969:32) at async NextNodeServer.pipeImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:920:25) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:272:17) at async NextNodeServer.handleRequestImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/lib/router-server.js:353:24) at async NextCustomServer.requestHandlerImpl [as requestHandler] (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/lib/router-server.js:377:13) { [cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: localhost:5055, timeout: 10000ms) at onConnectTimeout (/app/node_modules/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:232:24) at Immediate._onImmediate (/app/node_modules/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:206:11) at process.processImmediate (node:internal/timers:483:21) { code: 'UND_ERR_CONNECT_TIMEOUT' } }

SirBender avatar Jan 15 '25 14:01 SirBender

I am experiencing the same issue. @Fallenbagel your comment caused me to look at the docker logs and it seems like when internal jobs are running it is timing out because it can't reach itself on the configured localhost:30042. The port 30042 is pre-configured as the host port, when using the community app in TrueNAS. I am going to install Jellyseer now using docker compose in TrueNAS, keeping the default port mapping of 5055:5055 and see if that resolves the issue.

EDIT: Issue remains. Here the docker logs

2025-01-15T15:09:11.029Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch discover TV: fetch failed"} 2025-01-15T15:09:11.034Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: fetch failed"} 2025-01-15T15:09:11.035Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch discover movies: fetch failed"} ⨯ TypeError: fetch failed at node:internal/deps/undici/undici:13392:13 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async M.getInitialProps (/app/.next/server/chunks/51084.js:5:34051) at async X (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5045) at async e3 (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:25:3773) at async doRender (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1425:30) at async cacheEntry.responseCache.get.routeKind (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1599:28) at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1507:28) at async NextNodeServer.renderPageComponent (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1931:24) at async NextNodeServer.renderToResponseImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1969:32) at async NextNodeServer.pipeImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:920:25) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:272:17) at async NextNodeServer.handleRequestImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/lib/router-server.js:353:24) at async NextCustomServer.requestHandlerImpl [as requestHandler] (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/lib/router-server.js:377:13) { [cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: localhost:5055, timeout: 10000ms) at onConnectTimeout (/app/node_modules/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:232:24) at Immediate._onImmediate (/app/node_modules/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:206:11) at process.processImmediate (node:internal/timers:483:21) { code: 'UND_ERR_CONNECT_TIMEOUT' } }

Ah thats the undici timeout thing. You need to add these

dns:
   - 8.8.8.8
environment:
   - FORCE_IPV4_FIRST=true

to your compose. For some weird reason this is what makes it work for everyone who experienced the same issue which is why its documented in our troubleshooting. This comes from the newly migrated fetch library (we migrated from axios to fetch and it only happens in a few networking configurations and not even nodejs team knows why it happens so try these configurations first)

Refer to:

  • #1205
  • (and a looot of discord support threads with same error where adding these fixed it for them)

fallenbagel avatar Jan 15 '25 15:01 fallenbagel

Thanks, that seems to have resolved it for me. The DNS flag was not required, only used:

environment:
   - FORCE_IPV4_FIRST=true

SirBender avatar Jan 15 '25 15:01 SirBender

@jstewart3802 Could you try that as well?

fallenbagel avatar Jan 15 '25 16:01 fallenbagel

I added both and still have the issue as well. Running on Synology

docker run -d --name=jellyseerr
-p 5056:5055
-e PUID=1035
-e PGID=100
-e TZ=Europe/Paris
--dns 8.8.8.8
-e FORCE_IPV4_FIRST=true
-v /volume1/docker/jellyseerr:/app/config
--restart always
fallenbagel/jellyseerr

rsockanc avatar Jan 16 '25 05:01 rsockanc

I added both and still have the issue as well. Running on Synology

docker run -d --name=jellyseerr -p 5056:5055 -e PUID=1035 -e PGID=100 -e TZ=Europe/Paris --dns 8.8.8.8 -e FORCE_IPV4_FIRST=true -v /volume1/docker/jellyseerr:/app/config --restart always fallenbagel/jellyseerr

Could you send the docker logs when it crash

fallenbagel avatar Jan 16 '25 06:01 fallenbagel

Same issue. When I try to search for example in movie studio category, the title will be listed and short after 500 internal server error. Tried to check the docker logs but nothing in the docker logs. Checked syslog and found only one entry: Jan 19 18:57:12 NAS kernel: [ 3071.546089] traps: node[49303] trap invalid opcode ip:7f1cc69dd535 sp:7ffe97c192c0 error:0 in libvips-cpp.so.42[7f1cc67b5000+a4b000]

Used jellyseerr as docker container running system are: Ubuntu 22.04.05 LTS

Is there any workaround for that because it seems that my CPU does not support the used instruction set. Currently using an old mini ITX board with an integrated AMD E2-2000 APU which seems to be 12 years old by now.

Update: If I wait until Jellyseerr is up and running again and the browser established the page by himself, the page and the titles will be displayed without an error. Also, the lazy load of the next titles are working. The error occurs again, if I reload the hole page manually again.

kevinrode avatar Jan 19 '25 18:01 kevinrode

Same issue. When I try to search for example in movie studio category, the title will be listed and short after 500 internal server error. Tried to check the docker logs but nothing in the docker logs. Checked syslog and found only one entry: Jan 19 18:57:12 NAS kernel: [ 3071.546089] traps: node[49303] trap invalid opcode ip:7f1cc69dd535 sp:7ffe97c192c0 error:0 in libvips-cpp.so.42[7f1cc67b5000+a4b000]

Used jellyseerr as docker container running system are: Ubuntu 22.04.05 LTS

Is there any workaround for that because it seems that my CPU does not support the used instruction set.

I see. Which cpu? (I don't think there is a workaround if your cpu does not supposed the used instruction set as this is a nextjs managed app)

Also this might not be related. The OPs issue could be something else too like there was one other user who had similar issue as OP and it turned out that they were running out of memory as their container was set to 268MB.

fallenbagel avatar Jan 19 '25 18:01 fallenbagel

Mine crashed while running in Docker on a Synology DS1513+ with an INTEL Atom D2700 from 2013. I solved my issue by installing Docker on a PC with a CPU 11 years newer and now it works fine.

rsockanc avatar Jan 20 '25 05:01 rsockanc

This error is related to the use of a proxy server and CORS rules. Check this out: https://blog.logrocket.com/fetch-api-node-js/#common-errors, specifically the "Network and CORS issues in Fetch" section.

rbrgmn avatar Jan 22 '25 12:01 rbrgmn

Same issue. When I try to search for example in movie studio category, the title will be listed and short after 500 internal server error. Tried to check the docker logs but nothing in the docker logs. Checked syslog and found only one entry: Jan 19 18:57:12 NAS kernel: [ 3071.546089] traps: node[49303] trap invalid opcode ip:7f1cc69dd535 sp:7ffe97c192c0 error:0 in libvips-cpp.so.42[7f1cc67b5000+a4b000] Used jellyseerr as docker container running system are: Ubuntu 22.04.05 LTS Is there any workaround for that because it seems that my CPU does not support the used instruction set.

I see. Which cpu? (I don't think there is a workaround if your cpu does not supposed the used instruction set as this is a nextjs managed app)

Also this might not be related. The OPs issue could be something else too like there was one other user who had similar issue as OP and it turned out that they were running out of memory as their container was set to 268MB.

Its a ASUS E2KM1I with a integrated AMD E2 Accelerated Processor

kevinrode avatar Jan 23 '25 18:01 kevinrode

I am currently experiencing this same issue. Radarr, Sonarr, Jellyfin are all working as expected but Jellyseerr is slow, hangs, and starts throwing these errors left and right. I have tried both combos of

dns: 
  - 8.8.8.8 # or 1.1.1.1
environment:
  ... 
  - FORCE_IPV4_FIRST=true

added to my docker-compose with no fix. Nothing has changed with my home setup, and this just started a few days ago and has not worked since.

cgibsonmm avatar Jan 30 '25 22:01 cgibsonmm

I am currently experiencing this same issue. Radarr, Sonarr, Jellyfin are all working as expected but Jellyseerr is slow, hangs, and starts throwing these errors left and right. I have tried both combos of

dns: 
  - 8.8.8.8 # or 1.1.1.1
environment:
  ... 
  - FORCE_IPV4_FIRST=true

added to my docker-compose with no fix. Nothing has changed with my home setup, and this just started a few days ago and has not worked since.

Hop onto discord. Because

few days ago

We didn't change anything few days ago so your issue sounds different.

fallenbagel avatar Jan 31 '25 05:01 fallenbagel

I too am having the same issue.

At first I thought I was low on disk space (I needed to expand my vm volume anyway) so I did that but the issue continued.

Seems to happen when its trying to fetch some movie information.

I tried enabling Forice IPv4 but the issue continues.

_jellyseerr_logs.txt

aloskam88 avatar Feb 22 '25 04:02 aloskam88

I too am having the same issue.

At first I thought I was low on disk space (I needed to expand my vm volume anyway) so I did that but the issue continued.

Seems to happen when its trying to fetch some movie information.

I tried enabling Forice IPv4 but the issue continues.

_jellyseerr_logs.txt

What is the age of the CPU you are running this on?

rsockanc avatar Feb 22 '25 05:02 rsockanc

What is the age of the CPU you are running this on?

I'm having the same issue, the CPU is Intel Xeon E5-2680 v4 and v3 (at least I think it fails on both). I'm running Jellyseer in Kubernetes, that's running on virtualized Talos Linux. I'm passing in the CPU as host, not as x86_64-v2.

frantathefranta avatar Feb 22 '25 16:02 frantathefranta

What is the age of the CPU you are running this on?

I'm having the same issue, the CPU is Intel Xeon E5-2680 v4 and v3 (at least I think it fails on both). I'm running Jellyseer in Kubernetes, that's running on virtualized Talos Linux. I'm passing in the CPU as host, not as x86_64-v2.

Beats off of my personal experience and testing as well as reading through this post, my assumption is that a CPU from 2016 may not have the instruction set that one of the package components is looking for. Potentially try running on a system with a CPU that is 5 years old or newer.

rsockanc avatar Feb 22 '25 17:02 rsockanc

Beats off of my personal experience and testing as well as reading through this post, my assumption is that a CPU from 2016 may not have the instruction set that one of the package components is looking for. Potentially try running on a system with a CPU that is 5 years old or newer.

That's a valid point, however I've not really had any issues with any other software crashing because of missing CPU instructions. How would one go about figuring out what's missing?

frantathefranta avatar Feb 22 '25 18:02 frantathefranta

Beats off of my personal experience and testing as well as reading through this post, my assumption is that a CPU from 2016 may not have the instruction set that one of the package components is looking for. Potentially try running on a system with a CPU that is 5 years old or newer.

That's a valid point, however I've not really had any issues with any other software crashing because of missing CPU instructions. How would one go about figuring out what's missing?

Can you first try to exec into container and ping api.github.com

fallenbagel avatar Feb 22 '25 20:02 fallenbagel

I too am having the same issue. At first I thought I was low on disk space (I needed to expand my vm volume anyway) so I did that but the issue continued. Seems to happen when its trying to fetch some movie information. I tried enabling Forice IPv4 but the issue continues. _jellyseerr_logs.txt

What is the age of the CPU you are running this on?

Just hit 4 years. It's a Intel® Celeron® Processor N4505.

Same chipset and architecture used in a number of NAS.

So it's not very old.

I'm running Jellyseer in docker container on a vm within Proxmox.

aloskam88 avatar Feb 23 '25 09:02 aloskam88

Can you first try to exec into container and ping api.github.com

No issues with that.

frantathefranta avatar Feb 23 '25 20:02 frantathefranta

No issues pinging from container.

/app # ping api.github.com PING api.github.com (4.237.22.34): 56 data bytes 64 bytes from 4.237.22.34: seq=0 ttl=114 time=19.029 ms 64 bytes from 4.237.22.34: seq=1 ttl=114 time=18.976 ms 64 bytes from 4.237.22.34: seq=2 ttl=114 time=19.114 ms 64 bytes from 4.237.22.34: seq=3 ttl=114 time=19.417 ms 64 bytes from 4.237.22.34: seq=4 ttl=114 time=23.783 ms 64 bytes from 4.237.22.34: seq=5 ttl=114 time=21.012 ms ^C --- api.github.com ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 18.976/20.221/23.783 ms

aloskam88 avatar Feb 23 '25 22:02 aloskam88

I would suggest hopping onto discord to try and troubleshoot. Because we can't reproduce this and will need to troubleshoot vicariously through you to try and see where this is coming from

fallenbagel avatar Feb 24 '25 05:02 fallenbagel

OK I will do that.

aloskam88 avatar Feb 24 '25 13:02 aloskam88

I've been following this issue because my Jellyseerr server started to fail after a month of usage. I checked a lot of things related to the network connection, DNS, API keys to sonarr/radarr and I didn't find anything relevant.

I downloaded the same Docker image in my laptop, started the setup from 0 and it worked fine without any issues without changing anything. So, I went to my server and deleted the config/ folder and restart the container. I followed the setup and everything started working again. I'm unsure what was going on but it seems the configuration was busted for some reason 🤷🏼

humitos avatar Feb 26 '25 19:02 humitos

With Fallenbagels' help we seem to have determined the cause of the issue. Initially I had tried your step @humitos but that didn't do the trick for me.

I had to add the following to my docker-compose instead:

dns: - 8.8.8.8

He then linked me this article which essentially outlines why this is recommended: https://docs.jellyseerr.dev/troubleshooting#tmdb-failed-to-retrievefetch-xxx

Fallenbagel also explained why this happens, sort-of: "Nodejs and dns in certain docker networking setups been finicky and even nodejs team doesn't know why. Undici is timing out way too soon when dns resolution takes a little while"

Golden Rule - "It's not DNS. There's no way it's DNS. It was DNS".

The container is now stable and I am no longer getting errors in my container logs.

Cheers @fallenbagel , you're a legend :)

aloskam88 avatar Feb 27 '25 08:02 aloskam88

Hi, Just wanted to thank you guys. Was facing the same problem for at least some months now, tried VPN, other Docker Images and nothing. Sometimes Jellyseerr would work, others would hang and crash.

I've tried first with only FORCE_IPV4_FIRST=true but no dice. As soon as I set the DNS it started working perfectly fine again.

Cheers, thank you all for the hard work and amazing efforts!

ahskur avatar Mar 03 '25 10:03 ahskur

I also have the similar issue with random 500 errors. The response was the same like:

I am experiencing the same issue. @fallenbagel your comment caused me to look at the docker logs and it seems like when internal jobs are running it is timing out because it can't reach itself on the configured localhost:30042. The port 30042 is pre-configured as the host port, when using the community app in TrueNAS. I am going to install Jellyseer now using docker compose in TrueNAS, keeping the default port mapping of 5055:5055 and see if that resolves the issue.

EDIT: Issue remains. Here the docker logs

2025-01-15T15:09:11.029Z [debug][API]: Something went wrong retrieving the series genre slider {"errorMessage":"[TMDB] Failed to fetch discover TV: fetch failed"} 2025-01-15T15:09:11.034Z [debug][API]: Something went wrong retrieving popular series {"errorMessage":"[TMDB] Failed to fetch discover TV: fetch failed"} 2025-01-15T15:09:11.035Z [debug][API]: Something went wrong retrieving the movie genre slider {"errorMessage":"[TMDB] Failed to fetch discover movies: fetch failed"} ⨯ TypeError: fetch failed at node:internal/deps/undici/undici:13392:13 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async M.getInitialProps (/app/.next/server/chunks/51084.js:5:34051) at async X (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:16:5045) at async e3 (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:25:3773) at async doRender (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1425:30) at async cacheEntry.responseCache.get.routeKind (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1599:28) at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1507:28) at async NextNodeServer.renderPageComponent (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1931:24) at async NextNodeServer.renderToResponseImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1969:32) at async NextNodeServer.pipeImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:920:25) at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:272:17) at async NextNodeServer.handleRequestImpl (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:816:17) at async invokeRender (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/lib/router-server.js:174:21) at async handleRequest (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/lib/router-server.js:353:24) at async NextCustomServer.requestHandlerImpl [as requestHandler] (/app/node_modules/.pnpm/[email protected]_@[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/lib/router-server.js:377:13) { [cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: localhost:5055, timeout: 10000ms) at onConnectTimeout (/app/node_modules/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:232:24) at Immediate._onImmediate (/app/node_modules/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:206:11) at process.processImmediate (node:internal/timers:483:21) { code: 'UND_ERR_CONNECT_TIMEOUT' } }

until I add

dns:

  • 8.8.8.8 # or 1.1.1.1 environment: ...
  • FORCE_IPV4_FIRST=true

So, after specifying the DNS as 8.8.8.8 the exception stack trace was gone and I only get 500 errors with 0 additional information.

Running under Docker in Windows 11 with WSL2.

Here are what my docker logs looks like:

2025-06-05T00:58:51.422Z [debug][API]: Something went wrong retrieving languages {"errorMessage":"[TMDB] Failed to fetch langauges: fetch failed"}
2025-06-05T00:58:51.432Z [debug][API]: Something went wrong retrieving regions {"errorMessage":"[TMDB] Failed to fetch countries: fetch failed"}
2025-06-05T00:58:58.538Z [info][Jobs]: Starting scheduled job: Jellyfin Recently Added Scan 
2025-06-05T00:58:58.538Z [info][Jellyfin Sync]: Jellyfin Sync Starting {"sessionId":"59d82442-cba6-4b67-a6a6-e72c190d47f7"}
2025-06-05T00:58:58.573Z [info][Jellyfin Sync]: Beginning to process recently added for library: Movies 
2025-06-05T00:58:58.583Z [info][Jellyfin Sync]: Beginning to process recently added for library: Shows 
2025-06-05T00:58:58.586Z [info][Jellyfin Sync]: Recently Added Scan Complete 
2025-06-05T00:59:00.003Z [debug][Jobs]: Starting scheduled job: Download Sync 
2025-06-05T00:59:01.507Z [info][Jobs]: Starting scheduled job: Jellyfin Full Scan 
2025-06-05T00:59:01.508Z [info][Jellyfin Sync]: Jellyfin Sync Starting {"sessionId":"737895fa-23b9-4b33-8288-af8c2e701369"}
2025-06-05T00:59:01.541Z [info][Jellyfin Sync]: Beginning to process library: Movies 
2025-06-05T00:59:01.558Z [info][Jellyfin Sync]: Beginning to process library: Shows 
2025-06-05T00:59:01.579Z [info][Jellyfin Sync]: Full Scan Complete 
2025-06-05T00:59:04.402Z [info][Jobs]: Starting scheduled job: Radarr Scan 
2025-06-05T00:59:04.403Z [info][Radarr Scan]: Scan starting {"sessionId":"dd5fba9f-527b-468c-846c-d68a0f4cfe6e"}
2025-06-05T00:59:04.403Z [info][Radarr Scan]: Beginning to process Radarr server: Radarr 
2025-06-05T00:59:04.431Z [debug][Radarr Scan]: Title is unmonitored and has not been downloaded. Skipping item. {"title":"Движение вверх"}
2025-06-05T00:59:04.516Z [debug][Radarr Scan]: Saved new media: Дюна 
2025-06-05T00:59:08.517Z [info][Radarr Scan]: Radarr scan complete 
2025-06-05T00:59:09.734Z [info][Jobs]: Starting scheduled job: Sonarr Scan 
2025-06-05T00:59:09.735Z [info][Sonarr Scan]: Scan starting {"sessionId":"20c09b92-eaae-4c18-b671-f448be9d4a79"}
2025-06-05T00:59:09.735Z [info][Sonarr Scan]: Beginning to process Sonarr server: Sonarr 
2025-06-05T00:59:09.755Z [info][Sonarr Scan]: Sonarr scan complete 
2025-06-05T00:59:11.774Z [info][Jobs]: Starting scheduled job: Sonarr Scan 
2025-06-05T00:59:11.775Z [info][Sonarr Scan]: Scan starting {"sessionId":"af025c95-b1c6-4000-8403-2711269216e7"}
2025-06-05T00:59:11.775Z [info][Sonarr Scan]: Beginning to process Sonarr server: Sonarr 
2025-06-05T00:59:11.775Z [info][Sonarr Scan]: Sonarr scan complete 
2025-06-05T00:59:15.518Z [info][Jobs]: Starting scheduled job: Media Availability Sync 
2025-06-05T00:59:15.519Z [info][AvailabilitySync]: Starting availability sync... 
2025-06-05T00:59:15.578Z [info][AvailabilitySync]: Availability sync complete. 
2025-06-05T00:59:19.542Z [debug][Jobs]: Starting scheduled job: Download Sync 
2025-06-05T00:59:21.261Z [info][Jobs]: Starting scheduled job: Download Sync Reset 
2025-06-05T00:59:23.241Z [info][Jobs]: Starting scheduled job: Image Cache Cleanup 
2025-06-05T00:59:23.243Z [error][Image Cache]: ENOENT: no such file or directory, scandir '/app/config/cache/images/tmdb' 
2025-06-05T00:59:23.243Z [info][Image Cache]: Cleared 0 stale image(s) from cache 'tmdb' 
2025-06-05T00:59:23.249Z [info][Image Cache]: Cleared 0 stale image(s) from cache 'avatar' 
Warning: data for page "/settings/jobs" is 299 kB which exceeds the threshold of 256 kB, this amount of data can reduce performance.
See more info here: [https://nextjs.org/docs/messages/large-page-data⁠](https://nextjs.org/docs/messages/large-page-data)

Image

@fallenbagel I can jump into discord for some investigations on this issue on my local env if needed

tokKurumi avatar Jun 05 '25 01:06 tokKurumi

@tokKurumi please try develop tag. And jump into discord. This is still network related as I am able to access tmdb api properly

Ps. If youre in a country like india, then you might be having intermittent issues with tmdb api through your isp and the only fix for that is vpn/http proxy. If not then this is definitely just a network issue that can be fixable and please use discord for support requests.

fallenbagel avatar Jun 05 '25 01:06 fallenbagel