Excessive RAM consumption

[TheDreadPirate]

@thymon - One thing that may or may not be related, you have a client that has an expired token that is constantly failing authentication.

It also looks like you're having issues with your TV Guide provider. With images only from the error messages. Thousands of error messages and failed connection attempts. They make up nearly your entire log.

Actually, it looks like you have connectivity issues, in general. I see a lot of logs about Jellyfin not being able to query TVDB. Same with OpenSubtitles.

I'm wondering if all these failed connection attempts are the problem.

[thymon]

@thymon - One thing that may or may not be related, you have a client that has an expired token that is constantly failing authentication.

It also looks like you're having issues with your TV Guide provider.  With images only from the error messages.  Thousands of error messages and failed connection attempts.  They make up nearly your entire log.

Actually, it looks like you have connectivity issues, in general.  I see a lot of logs about Jellyfin not being able to query TVDB.  Same with OpenSubtitles.

I'm wondering if all these failed connection attempts are the problem.

Thanks for your analysis.
Regarding the EPG, I’ve removed it from Jellyfin and moved it to the IPTV proxy. That should already eliminate this issue.
For the client with an expired token, what should I do? Same for the connections with TVDB and OpenSubtitles—I depend on their APIs, so there’s not much I can do. 😞

[TheDreadPirate]

For the expired token, find the device and log out and back in. It is probably an Android TV device.

For TVDB and OpenSubtitles, is IPv6 enabled in Jellyfin? What I often see if that there is a mismatch between the host and Jellyfin. Usually the host has IPv6 enabled, but it isn't enabled in Jellyfin.

[thymon]

For the expired token, find the device and log out and back in.  It is probably an Android TV device.

It's never the same devices, and since the server reboots at least once a day, they all get disconnected anyway.
Today, I encountered this error, which flooded the logs and caused RAM usage to spike within minutes:

Code:

[2025-03-28 12:04:00.621 +01:00] [ERR] [479] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Sessions/Playing/Progress".
[2025-03-28 12:04:00.742 +01:00] [ERR] [468] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Sessions/Playing/Progress".
[2025-03-28 12:04:00.748 +01:00] [ERR] [468] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Sessions/Playing/Progress".
[2025-03-28 12:04:01.569 +01:00] [ERR] [469] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Sessions/Playing/Progress".
[2025-03-28 12:04:01.572 +01:00] [ERR] [469] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Sessions/Playing/Progress".
[2025-03-28 12:04:01.575 +01:00] [ERR] [469] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Sessions/Playing/Progress".
[2025-03-28 12:04:01.577 +01:00] [ERR] [469] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Sessions/Playing/Progress".
[2025-03-28 12:04:01.580 +01:00] [ERR] [469] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Sessions/Playing/Progress".
[2025-03-28 12:04:01.583 +01:00] [ERR] [469] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Sessions/Playing/Progress".
[2025-03-28 12:04:01.585 +01:00] [ERR] [469] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST"

How should I interpret this, and how can I prevent it?
Could there be something to investigate on the reverse proxy side?
Here’s what I’ve applied to my NPM :

Code:

    # Disable buffering when the nginx proxy gets very resource heavy upon streaming
    proxy_buffering off;

    # Proxy main Jellyfin traffic
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-Protocol $scheme;
    proxy_set_header X-Forwarded-Host $http_host;
    proxy_headers_hash_max_size 2048;
    proxy_headers_hash_bucket_size 128;
   
    # Security / XSS Mitigation Headers
    add_header X-Content-Type-Options "nosniff";

    # Content Security Policy
    # See: https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
    # Enforces https content and restricts JS/CSS to origin
    # External Javascript (such as cast_sender.js for Chromecast) must be whitelisted.
    add_header Content-Security-Policy "default-src https: data: blob: ; img-src 'self' https://* ; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://www.gstatic.com https://www.youtube.com blob:; worker-src 'self' blob:; connect-src 'self'; object-src 'none'; frame-ancestors 'self'; font-src 'self'";

For TVDB and OpenSubtitles, is IPv6 enabled in Jellyfin?  What I often see if that there is a mismatch between the host and Jellyfin.  Usually the host has IPv6 enabled, but it isn't enabled in Jellyfin.

No IPv6 enabled on my server

[TheDreadPirate]

The token issue is not related to disconnects. Tokens can expire or are revoked, but our TV clients will continue to attempt to log in in the background until you explicitly open the app and re-enter credentials.

Regarding Nginx Proxy Manager. We've updated our docs and the code below is the only thing that should be in the advanced tab.

Code:

# Disable buffering when the nginx proxy gets very resource heavy upon streaming
    proxy_buffering off;

The rest of what you have is not necessary and, AFAICT, doesn't actually do anything in Nginx Proxy Manager. If you have "cache assets" checked on the main configuration page, DISABLE it.

I don't know whether the "unexpected end" messages are related to Nginx.

Regarding IPv6. So you're saying that unRAID doesn't have IPv6 at all? Or that it isn't enabled in Jellyfin?

Can you open the terminal for unRAID and type in this command? Share the output.

Code:

curl -vvv https://image.tmdb.org/t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg -o /tmp/futurama.jpg

[thymon]

The token issue is not related to disconnects.  Tokens can expire or are revoked, but our TV clients will continue to attempt to log in in the background until you explicitly open the app and re-enter credentials.

Noted, okay, but I don't know how to find this device...

Regarding Nginx Proxy Manager.  We've updated our docs and the code below is the only thing that should be in the advanced tab.

Code:

    # Disable buffering when the nginx proxy gets very resource heavy upon streaming
    proxy_buffering off;

Done ! Thx

Regarding IPv6.  So you're saying that unRAID doesn't have IPv6 at all?  Or that it isn't enabled in Jellyfin?

IPv6 is disable on my Unraid. Only Ipv4 used.

Can you open the terminal for unRAID and type in this command?  Share the output.

Code:

curl -vvv https://image.tmdb.org/t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg -o /tmp/futurama.jpg

Okay, it's done, I sent it to you in a private message.

Thank you very much for helping me find this issue.

[TheDreadPirate]

The host is receiving DNS results in IPv6. As shown by the DNS results for image.tmdb.org.

Code:

22:40:37.797387 [0-0] == Info: IPv6: 2400:52e0:1e02::1221:1
22:40:37.797459 [0-0] == Info: IPv4: 185.93.2.251

You need to ensure that either IPv6 is fully setup and enabled everywhere (this is what I do), or ensure that IPv6 is fully disabled everywhere. Including DNS.

As for the device that is continuously failing authentication. You're just going to have to go to each Android TV or Roku device, these are the typical culprits, and log out and log in. Or have all your remote users do the same.

[thymon]

The host is receiving DNS results in IPv6.  As shown by the DNS results for image.tmdb.org.

Code:

22:40:37.797387 [0-0] == Info: IPv6: 2400:52e0:1e02::1221:1
22:40:37.797459 [0-0] == Info: IPv4: 185.93.2.251

You need to ensure that either IPv6 is fully setup and enabled everywhere (this is what I do), or ensure that IPv6 is fully disabled everywhere.  Including DNS.

On my side, everything is disabled. If it's the DNS, then there's nothing I can do.
I'm using Cloudflare's 1.1.1.1, and IPv6 cannot be disabled on this free plan.

[TheDreadPirate]

You could also try going the other way and fully setup IPv6. Assuming your ISP and router allow it.

[evrial]

Unused memory is wasted memory.

This should be never used as argument to justify memory consumption and poor coding practices. The issue is critical and leads to OOM denial of service when swap is disabled even when Jellyfin never used.

[16:05:24] [INF] [4] Main: Jellyfin version: 10.10.7
[16:05:25] [INF] [4] Main: Environment Variables: ["[JELLYFIN_LOG_DIR, /home/dietpi/.local/share/jellyfin/log]"]
[16:05:25] [INF] [4] Main: Arguments: ["/usr/lib/jellyfin/bin/jellyfin.dll", "version"]
[16:05:25] [INF] [4] Main: Operating system: Debian GNU/Linux 12 (bookworm)
[16:05:25] [INF] [4] Main: Architecture: Arm64
[16:05:25] [INF] [4] Main: 64-Bit Process: True
[16:05:25] [INF] [4] Main: User Interactive: True
[16:05:25] [INF] [4] Main: Processor count: 4