Server crashing while browsing the UI #1252
Comments
jstewart3802
added
awaiting triage
|
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
added
question
|
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. EDIT: Issue remains. Here the docker logs
|
Ah thats the undici timeout thing. You need to add these 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:
|
|
Thanks, that seems to have resolved it for me. The DNS flag was not required, only used: |
|
@jstewart3802 Could you try that as well? |
|
I added both and still have the issue as well. Running on Synology docker run -d --name=jellyseerr |
Could you send the docker logs when it crash |
|
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: 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: |
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. |
|
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. |
|
This error is related to the use of a proxy server and CORS rules. |
Its a ASUS E2KM1I with a integrated AMD E2 Accelerated Processor |
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
Screenshots
No response
Logs
Platform
desktop
Database
None
Device
Windows PC
Operating System
Windows 11
Browser
Chrome
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: