SOLVED: DirectPlayError when behind reverse proxy webOS

[andreafontana]

Hi,

I'm having issues with my reverse proxy configuration. I have both Jellyfin and Nginx Reverse Proxy installed as docker containers on a Zimaboard, and I'm trying to use the official webOS app as client. On local network everything's fine. Outside local network, I can access the web UI from the LG TV, yet I'm experiencing Playback errors. Specifically, whenever I reproduce a file from the beginning, direct play starts and no problem occurs. As soon as I skip forwards or backwards or continue watching an already started film, transcoding is triggered (even though the file is compatible with the client) and I get an error saying "There was an error starting direct playback". All the other clients I tried work fine, so it's related to the webOS app.

I tried using plain nginx, as well as cloudflare tunnels, same behaviour. I followed the official guides on how to set up npm (also commented the lines that are may cause problems with webOS).

I tried opening a port and accessing jf from WANIP:port and this problem does not occur. 

I'm attaching ffmpeg log and the errors I get with cloudflare tunnels.
  cloudflare tunnels error.txt (Size: 949 bytes / Downloads: 16)
  log.txt (Size: 60.3 KB / Downloads: 20)

Any ideas? 

Thank you,

Andrea

[TheDreadPirate]

In NPM, can you remove all of the "add_header" advanced options?

These.

Code:

# Security / XSS Mitigation Headers
    # NOTE: X-Frame-Options may cause issues with the webOS app
    add_header X-Frame-Options "SAMEORIGIN";
    add_header X-XSS-Protection "0";
    add_header X-Content-Type-Options "nosniff";

[andreafontana]

In NPM, can you remove all of the "add_header" advanced options?

These.

Code:

    # Security / XSS Mitigation Headers
    # NOTE: X-Frame-Options may cause issues with the webOS app
    add_header X-Frame-Options "SAMEORIGIN";
    add_header X-XSS-Protection "0";
    add_header X-Content-Type-Options "nosniff";

I tried already, but didn't solve the issue

[TheDreadPirate]

Are you using https? If so, are you using legit certs or self-signed certs?

[andreafontana]

Yes, I'm using custom certificates generated through cloudflare

[andreafontana]

Update: I also tried setting up Caddy, with https ans got the same result, so I don't think it's due to the reverse proxy.

[TheDreadPirate]

When you're using caddy or nginx proxy manager, is your Cloudflare setup for DNS only or is it proxied?

[andreafontana]

proxied

[TheDreadPirate]

I'm pretty sure that CF's default proxy setup has some XSS/CSP going on that may be preventing your WebOS client from connecting. In the same way we've documented with Nginx and Apache.

Regardless, using CF's proxy for video streaming is against their TOS. I recommend switching to DNS only since you're already using https.

[andreafontana]

Yes that's it. I also had to generate certificates with let's encrypt.

Thank you for your help