2023-07-06, 10:30 AM
(This post was last modified: 2023-07-06, 01:45 PM by dupl0. Edited 8 times in total.)
Jellyfin server version: latest version of docker image, stable
Jellyfin client version: LG TV WebOS app, latest
Access method: both via reverse proxy and via native SSL set up within Jellyfin
Hello,
I have setup the Jellyfin server and connected successfully to it via HTTP from my WebOS TV app.
After that I set up HTTPS via a reverse proxy on my Synology NAS, which also worked like a charm in my MacOS browser. However; the WebOS TV app refuses point blank to connect if I put in the FQDN of the reverse proxy and the correct port (the exact same domain and port part of the address line as the one that works in the browser).
I suspect it fails because the root certificate is not installed on the TV, but I still decided to try and add HTTPS natively instead effectively bypassing the reverse proxy.
Once again, in my browser my configuration works flawlessly
- but once I try that connection address in the WebOS TV app, no joy.
Anyone else had similar troubles and has a hint to were the trouble is?
I have seen in the forum some suggestions on the reverse proxy part that has not worked for me.
MUST the TV have the Root Certificate from my Home Root CA installed for this to work (can it not accept/prompt to use an untrusted cert to simply accomplish encrypted traffic)?
(reason I ask is because I do not use a commercial provider, only my "home CA". I also do not think the TV allows for installing custom Root CAs unless you go through some hassle with developer mode).
Or is there something else I am missing?
On my home network I guess I can live with HTTP, but then I miss out on all the remote capability via the internet (if connecting with WebOS).
Jellyfin client version: LG TV WebOS app, latest
Access method: both via reverse proxy and via native SSL set up within Jellyfin
Hello,
I have setup the Jellyfin server and connected successfully to it via HTTP from my WebOS TV app.
After that I set up HTTPS via a reverse proxy on my Synology NAS, which also worked like a charm in my MacOS browser. However; the WebOS TV app refuses point blank to connect if I put in the FQDN of the reverse proxy and the correct port (the exact same domain and port part of the address line as the one that works in the browser).
I suspect it fails because the root certificate is not installed on the TV, but I still decided to try and add HTTPS natively instead effectively bypassing the reverse proxy.
Once again, in my browser my configuration works flawlessly
- but once I try that connection address in the WebOS TV app, no joy.
Anyone else had similar troubles and has a hint to were the trouble is?
I have seen in the forum some suggestions on the reverse proxy part that has not worked for me.
MUST the TV have the Root Certificate from my Home Root CA installed for this to work (can it not accept/prompt to use an untrusted cert to simply accomplish encrypted traffic)?
(reason I ask is because I do not use a commercial provider, only my "home CA". I also do not think the TV allows for installing custom Root CAs unless you go through some hassle with developer mode).
Or is there something else I am missing?
On my home network I guess I can live with HTTP, but then I miss out on all the remote capability via the internet (if connecting with WebOS).