2023-07-06, 12:48 PM
(This post was last modified: 2023-07-08, 05:57 AM by dupl0. Edited 3 times in total.)
UPDATE: I tested going towards the Jellyfin HTTPS DNS address + port via the TV browser and that worked (displaying a "sure you wanna continue" and I could proceed).
This variant instead failed on the authentication for some strange reason - but that could be limitations in the proprietary browser installed on the TV, I expect this browser is pretty rudimental/simple.
Anyhow, I am left with this problem being due to the certificate not being trusted?
If that is the case, I think the app on LG WebOS should be able to establish https (via user warning) in cases where cert is either self-signed or untrusted due to lack of root cert - just in order to get encrypted auth over a home network.
I also found out that installing custom root certs on the TV is not possible without rooting the TV.
So installing root certs is not possible to do via developer mode.
Tried "forcing" HTTPS - and instead pointing the app to HTTP only to be redirected to HTTPS, to no avail
This variant instead failed on the authentication for some strange reason - but that could be limitations in the proprietary browser installed on the TV, I expect this browser is pretty rudimental/simple.
Anyhow, I am left with this problem being due to the certificate not being trusted?
If that is the case, I think the app on LG WebOS should be able to establish https (via user warning) in cases where cert is either self-signed or untrusted due to lack of root cert - just in order to get encrypted auth over a home network.
I also found out that installing custom root certs on the TV is not possible without rooting the TV.
So installing root certs is not possible to do via developer mode.
Tried "forcing" HTTPS - and instead pointing the app to HTTP only to be redirected to HTTPS, to no avail