Shield and SSL

[marpow]

Has anyone successfully got a Let's Encrypt certificate working with the Jellyfin client on the Nvidia Shield Pro? I setup Jellyfin on Debian and have a p12 certificate from Let's Encrypt with the correct hostname working for web browser and iOS client access. When I try from my Shield it says it cannot connect. Is the Shield missing the Let's Encrypt root certificate?

Thank in advance!

[TheDreadPirate]

We strongly recommend NOT using Jellyfin's built in HTTPS functionality. It is deprecated and will be removed entirely in JF 13. We recommend you use a reverse proxy like Caddy or Nginx. It is much more secure and configurable. What is likely happening is that the cert you are using does not include the full certificate chain. Your Shield likely does not explicitly trust the intermediate cert, but the cert you provide does not include the root certificate, which your Shield almost certainly does trust.

Use a reverse proxy for handling https connections (see documentation below). But for LAN client, https is not necessary.

https://jellyfin.org/docs/general/post-i...rse-proxy/

[marpow]

Thanks for the feedback. I was hoping to avoid the overhead of running Jellyfin through a reverse proxy. I have other, lighter weight services going through a Nginx proxy, but those have significantly lower bandwidth utilization. I've transitioned to running almost all services, both remote and local, as encrypted for consistency, particularly anything that passes authentication information.

[TheDreadPirate]

Unless this is a really really low powered system, the overhead from Nginx handling TLS traffic, even for jellyfin, is negligible. All my Jellyfin clients, even clients on my LAN, go through Nginx. When I am monitoring btop, Nginx is so far down the list of processes (sorted by CPU usage), that I have never actually seen it pop up. Nginx is incredibly efficient.