2024-10-18, 06:03 PM
(This post was last modified: 2024-10-18, 06:04 PM by andreafontana. Edited 1 time in total.)
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: 9)
log.txt (Size: 60.3 KB / Downloads: 11)
Any ideas?
Thank you,
Andrea
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.
![Text Document .txt](https://static.jellyfin.org/forum/images/attachtypes/txt.png)
![Text Document .txt](https://static.jellyfin.org/forum/images/attachtypes/txt.png)
Any ideas?
Thank you,
Andrea