SOLVED: Firetick App

[TheDreadPirate]

You may need to use a different reverse proxy. Nginx Proxy Manager is my recommendation. The issue, I think, is that your Firestick probably hasn't received any security updates in a while. Those updates usually include updates to root and intermediate certificate authorities. Let's Encrypt's intermediate authority refreshed in March 2024. If the DSM proxy isn't sending the client the root certificate, only the server and intermediate certificates, then your Firestick won't trust the cert.

In many reverse proxies, you can configure what certs to send to the client. But it does not appear that the DSM proxy can.

[dess4k]

Latest FireOS installed (7.6.8.5). Still not working
Tried on a android TV (0.18.4) on Philips 65OLED887. Worked with no trouble
So my config looks good and I think again the problem comme from the FireStick app....
2 apps are available on the amazon store 'Jellyfin for Fire TV' and 'JellyFin', any différence between these 2 apps ?

---

thanks TheDreadPirate
(I wrote my last post before seing yours)
Will have a look at Nginx Proxy Manager, but other apps with the same certificate installed on my NAS are accessible from a firesick...

[TheDreadPirate]

Yes. For the reasons I stated, I don't the Firestick is able to trust the certificate you're using without additional configuration that the DSM proxy isn't able to provide.

The "Jellyfin" app is probably the standard Android app (intended for phones and tablets).

[dess4k]

ok so,
I cant install docker in my nas because of the type of FileSystem I used years ago during the initial setup.
Installing Nginx Proxy Manager on a raspberry pi could make the trick ?
What would be the configuration I should add in Nginx Proxy Manager to make the SSL certificat work properly ?

[TheDreadPirate]

Running Nginx on an Rpi is fine. On any other PC you have, really.

I can't remember which is the setting that "fixes" this issue, but all three of these should be present in the nginx config.

Code:

ssl_certificate /etc/letsencrypt/live/domain.tld/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/domain.tld/privkey.pem; # managed by Certbot
    ssl_trusted_certificate /etc/letsencrypt/live/domain.tld/chain.pem; # managed by Certbot

[dess4k]

Hi TheDreadPirate
I think I am good with nginx proxy manager configuration now (installed on docker within a RaspberryPI).
I created a domain name in Duckdns, and set up everything with LE certificate in NPM.
Still need to test/validate with the device not able to reach out the Jellythin server using the Duckdns domain name now.

I saw many tutorials talking about going through Cloudflare (in between the client and my router - See attachment).

Any advice on that ?

[TheDreadPirate]

Do not use Cloudflare with Jellyfin. It is against their TOS to serve video/audio through the free tier proxy service.

[dess4k]

ok got it thanks

[dess4k]

Thanks TheDreadPirate
Using NPM and duckdns make the tricks.