rbjtech 4265 Posted January 25 Share Posted January 25 (edited) 27 minutes ago, visproduction said: Related? https://thetechgorilla.com/lg-tv-streaming-issues/ https://tvnoob.com/lg-tv-server-certificate-has-expired-error/#google_vignette If it never connected - then I'd say a possibility - but it connects and allows browsing - it just fails to play. I'd suggest it's websocket related - something incompatible between the Synology RP and LG App for some reason ... ? Edited January 25 by rbjtech 1 Link to comment Share on other sites More sharing options...
Luke 37066 Posted January 25 Share Posted January 25 5 hours ago, rbjtech said: If it never connected - then I'd say a possibility - but it connects and allows browsing - it just fails to play. I'd suggest it's websocket related - something incompatible between the Synology RP and LG App for some reason ... ? Yes that still could be possible and no it's not websocket related. The reason it still could be possible is that it's very common for devices to have separate networking stacks for their audio/video players compared to the rest of the system. Reason being because usually it's some kind of cross-platform a/v player with everything self-contained, including the networking. So that's why could you see the UI accept an SSL certificate but then the player reject it. 2 Link to comment Share on other sites More sharing options...
SamES 890 Posted January 26 Share Posted January 26 3 hours ago, Luke said: So that's why could you see the UI accept an SSL certificate but then the player reject it. And that is what I expect is happening - I have seen others with similar experiences discover exactly this as being the problem 1 Link to comment Share on other sites More sharing options...
visproduction 122 Posted January 26 Share Posted January 26 On 1/25/2024 at 7:52 AM, rbjtech said: If it never connected - then I'd say a possibility - but it connects and allows browsing - it just fails to play I think if the playback is part of a SSL certificate, then that alone could fail even when the browser sees the rest of the page. I would guess that the mismatch depands on how strict of policy the LG TV environment is on what it allows if there is mixed http and https content. Perhaps calling out a secure stream from otherwise http page causing the playback to be blocked. I think it's worth troubleshooting with the suggestions in the links I mentioned because code created by the TV OS is probably written to stop any streams that are not perfect, so LG has less support to do for clients who try strange combinations. I have not seen the code, nor tried any tests, just a guess. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now