jellyfin-webos: Unable to Connect [webOS 3.0, 3.5, more?]

Hi, sorry if it bothers you, but do you think there is any chance to bring Jellyfin to the VIDAA system?

So far VIDAA have been refusing to answer my requests for documentation, so currently there is no chance. Feel free to request such a feature though. Not sure what the official Github way of submitting such a request would be. Probably not the WebOS repo.

The correct location for such a request would be https://features.jellyfin.org/, so please create a feature request there. Please include any appropriate information and links.

From a quick look at their website, it looks like the Jellyfin team would have to communicate with VIDAA in an official capacity to get access to documentation and development resources, so there is no reason for you to contact them directly about a Jellyfin app, that might complicate things for us in the future.

We’re still working on getting the LG webOS and Samsung Tizen apps into the stores, so it is unlikely VIDAA will get much priority before that is done.

In #50, @agrisci has figured out the issue. It looks like we need to enable older protocols for SSL for the internal testing server.

https://github.com/jellyfin/jellyfin-webos/issues/50#issuecomment-821836996

… The correct location for such a request would be https://features.jellyfin.org/, so please create a feature request there. Please include any appropriate information and links.

Thanks and sorry for the inconvenience. I’m not good with Github. Anyway, I got the following answer: “… you will need to consult with our technical support team at global.hisense.com/support/customer-center.” So it’s not like I got anything either. Regards!

So far VIDAA have been refusing to answer my requests for documentation, so currently there is no chance. Feel free to request such a feature though. Not sure what the official Github way of submitting such a request would be. Probably not the WebOS repo.

Thank you, I just send a message to the VIDAA support. Have a nice day!

Hi, sorry if it bothers you, but do you think there is any chance to bring Jellyfin to the VIDAA system?

So far VIDAA have been refusing to answer my requests for documentation, so currently there is no chance. Feel free to request such a feature though. Not sure what the official Github way of submitting such a request would be. Probably not the WebOS repo.

Thanks for your update @anthonylavado. As long as it’s passing the certification your workaround will do just fine. Very few will be facing this issue anyway, so having it in the documentation will probably be good enough.

The exact error reported is net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH

ares-device-info

modelName : 49UH603V-ZE
sdkVersion : 3.3.0
firmwareVersion : 05.31.00
boardType : K2L_DVB_EU

Console output

Navigating 1...
http://demo.jellyfin.org false
GET https://demo.jellyfin.org/System/Info/Public net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Failure: Object {error: true}
Could not connect to server...
Failure: Object {error: 0}
Could not connect to server... 

As I mentioned before, while I appreciate all of the testing, this in particular isn’t the highest for the release issues because we’re just using a workaround for the time being.

Basically, for all of our vendor accounts (including Google Play, Apple App Store, etc) we have a private demo server that we provide for them to test with. It’s got mostly similar content to the public demo server (just a few items removed for rating reasons). On this private server, we’ve given the LG Testing IP range access to connect without HTTPS, solely for testing purposes.

We will eventually want to apply these cipher option fixes here and on the publicly accessible server. We’ll also use this info to make sure our Reverse Proxy guides have a notice and are up to date once the app releases, so that public users know what to expect. I’ll keep this issue open for tracking purposes, but I would deem it no longer “release critical”.

I’ve dealt a lot with SSL/TLS related problems in the past. This specific one could simply be a TLS handshake mismatch.

Your demo server supports the following cipher suites for TLS 1.2:

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

https://webostv.developer.lge.com/discover/specifications/web-engine/ states that WebOS 3.x uses a Chromium 38 engine which just might not be capable of using those ciphers.

I’d suggest adding something like this to the TLS 1.2 configuration on your demo server:

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

So there’s been a bunch of work behind the scenes. We’ve made sure that the internal and public demo servers are using TLS 1.2, as that is supported across all webOS versions.

From some more cursory searching on the internet, it seems that the app interface doesn’t like Let’s Encrypt certificates for some reason, even though the regular browser is okay with it. Since we use LE for all our sites, this is presenting an issue for us.

We’ve currently made alternate arrangements to provide LG with an HTTP URL for testing, but obviously we’ll still want to figure out how we can make this work for everyone.