Thildemar 0 Posted February 14, 2019 Share Posted February 14, 2019 Hello, I just got to the bottom of a couple remote Kodi systems failing playback about the time they updated to Kodi v18. I totally reset the systems with the latest Kodi build and Emby addon and could get sync to work, but no artwork would display and playback would just close without actually showing video. After looking in the logs I found lots of invalid SSL warnings, ex: \requests\packages\urllib3\connectionpool.py:791: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html InsecureRequestWarning) The invalid SSL was expected in my use case, but I went ahead and installed a new certificate on the server and the clients started working normally. Verify connection was turned OFF in addon settings for all of this testing. I did not find any workaround to use https with an expired or self signed certificate. I am assuming there is some form of bug with ssl validation still occurring for playback even with that option turned off in settings. I verified this behavior in both 4.0.5 and 4.0.6 beta. I also noticed with the newer builds there is no option to ignore SSL validation when initially connecting to the server. In order to get the connection established I had to cancel out of the initial "connect" screen, go to addon settings, then restart kodi and manually enter server details from the connection window. This behavior could likely be simplified. Thanks! Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted February 14, 2019 Share Posted February 14, 2019 (edited) What makes you think it has to do with Emby for Kodi? Edit: Is this maybe related? Seems to say that Kodi wasn't verifying certs before Leia. https://forum.kodi.tv/showthread.php?tid=331918 Edit2: The reason I say this is Emby for Kodi uses it's own version of requests. So if that is the path to requests you pasted in your post, it's not coming from Emby for Kodi... Edited February 14, 2019 by Angelblue05 Link to comment Share on other sites More sharing options...
Thildemar 0 Posted February 14, 2019 Author Share Posted February 14, 2019 What makes you think it has to do with Emby for Kodi? These systems only have media provided by emby for Kodi. They are fresh Kodi 18 installs with only the Emby for Kodi addon added. media playback is coming from an emby server via https I suppose the certificate refusal may be linked to changes in the playback engine in Kodi 18. I am not familiar enough with what parts of playback Emby addon handles vs the native functions. Even if this is the case It would be good to have it mentioned somewhere and probably remove the option to disable certificate validation if it no longer functions... Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted February 14, 2019 Share Posted February 14, 2019 Edit: Is this maybe related? Seems to say that Kodi wasn't verifying certs before Leia. https://forum.kodi.tv/showthread.php?tid=331918 Edit2: The reason I say this is Emby for Kodi uses it's own version of requests. So if that is the path to requests you pasted in your post, it's not coming from Emby for Kodi... The add-on doesn't handle anything beyond telling Kodi to play the file /path/to/file. Loading the file, etc that's all Kodi. Verify connection works. What you are seeing is likely the Kodi leia changes. They likely verify cert for artwork caching and playback now. At least according to the forum post, it seems like it. The reason I say this is Emby for Kodi uses it's own version of requests. So if that is the path to requests you pasted in your post, it's not coming from Emby for Kodi. Were you able to connect to your server? If so, then verify connection being disable works. 1 Link to comment Share on other sites More sharing options...
Thildemar 0 Posted February 14, 2019 Author Share Posted February 14, 2019 Thanks all, It does seem to be a change in Kodi. Seeing as I only use SSL sources with Emby I had no idea. It does look like some of their team is adding options to disable it on certain paths. Might be worth integrating the disable verification box with that when complete. Link to comment Share on other sites More sharing options...
Recommended Posts