[matthuisman]

"Temporary failure in name resolution"
So a DNS issue somewhere in your network.

If you don't want the add-on to Sync playback to Disney+, turn off "Sync with Disney+" and it won't send the progress every 20 seconds.
I will update it so it doesn't show an error if it fails to sync the playback though

UPDATE
just pushed 0.6.4 that wont show errors if the sync callback fails

[SurfSound]

Hello matthuisman,

thanks for the quick fix

But now I have another problem. I watched a movie yesterday and at about an hour in it stopped playing and seemed to buffer. Cause when I paused the movie for a short term it played again but not for long. I did try a lower quality but even then it stopps every few minutes. Then I checked my internet speed with speed tester and it told me I have ~28 mbit while for the best qualitiy available I should only need about 8 mbit. This thime I got no error messages. Any ideas?

[matthuisman]

Sounds like your internet isn't keeping up to be honest. Can't help sorry.

[PANiCnz]

Anyone else getting popups in Kodi advertising electric kiwi after installing addons from Matt’s repo?

[BlueMax1916]

Hi,

I have a problem after Disney+ 0.63 and SlyGuy Common 0.26.1 were updated to newer versions. I am running Kodi 19.1 portable on Windows 10 on several computers in my home network. I get this error every time I update to newer versions and try to get into a Disney+ menu like 'Watchlist':

ERROR <general>: slyguy.disney.plus - check_hostname requires server_hostname





If I reinstall the aforementioned versions it works all fine. I researched and I found out that if I bypass the Squid Proxy I run for website access in my home network the newer versions work o.k. too. But that is not an option here. The Gismeteo add-on seems to have the same problem, the Amazon VOD doesn't. I have set up proxy access centrally in Windows 10 proxy settings to pass every website access by any program on the computers here through the proxy.

Is there a solution for this problem? I can provide logs per PM if you wish. I have two portable Kodi 19.1 setups. One with the old add-on versions, one with the newest ones.

Cheers

Blue Max

[BlueMax1916]

There is no edit button: It is Disney+ 0.6.3 and SlyGuy Common 0.26.8.

[BlueMax1916]

Another try with the screenshot:



https://www.directupload.net/file/d/6185...rn_png.htm

[matthuisman]

@BlueMax1916 
I did recently update all my dependencies to their newer versions.
I note urllib3 1.26.4 (https://github.com/urllib3/urllib3/releases/tag/1.26.4) has
"The default SSLContext now sets check_hostname=True."

So i've just pushed update to slyguy common (0.30.2) reverting urllib3 back to 1.26.3
Could you update and let me know if that fixes for you?

[BlueMax1916]

Hi,

thank you for the fast assistance. I updated SlyGuy Common to 0.30.2 and restarted Kodi but unfortunately I got another error screen:

Part 1:



https://www.directupload.net/file/d/6185...jc_png.htm



Part 2:



https://www.directupload.net/file/d/6185...rm_png.htm


Cheers

Blue Max

[matthuisman]

Your proxy causing all sorts of issues with https.
Try going into the Disney+ addon settings > advanced and turn off verify certs

[BlueMax1916]

Your proxy causing all sorts of issues with https.
Try going into the Disney+ addon settings > advanced and turn off verify certs

Hi,

I disabled check for SSL-certificates but no joy, same error. Funny, it worked until the update described above. My proxy is Squid which is sort of a standard in Linux world. I am running this for years now to keep the smut from the internet off of my home network and my family. It is updated regularely. Everything works: https Websites with SSL certificates, home banking with SSL certificates, you name it. Also Amazon VOD works flawlessly using similar techniques as Disney+/SlyGuy Common. What is the main difference in the code now and then? What changed?

All I can see in the proxy logs is: 'error:invalid-request'. I do not even see which IP adress or hostname should get contacted.

Cheers

Blue Max

[matthuisman]

ok, try latest common (0.30.3)
i went back to 1.26.4 and made a small modification here:
https://github.com/matthuisman/slyguy.ad...5a6f157d94
which is from their latest master branch code.

Actually, don't think that will fix.
I can simulate the error by enabling windows proxy through charles.

UPDATE:
just pushed 0.30.5 of common that should fix it
this reverts urllib3 to 1.25.11. 
version after (1.26.0) breaks
pretty sure it's due to "Added support for HTTPS proxies contacting HTTPS servers"

[BlueMax1916]

...

UPDATE:
just pushed 0.30.5 of common that should fix it
this reverts urllib3 to 1.25.11. 
version after (1.26.0) breaks
pretty sure it's due to "Added support for HTTPS proxies contacting HTTPS servers"

Hi,

absolutely fantafabulous    That did the trick. It works again. Thank you for your assistance. It also works again on Kodi 18.9.

Cheers

Blue Max

[V8MEM]

@matthuisman it is actually this python urllib bug: https://bugs.python.org/issue42627

[matthuisman]

@V8MEM

thanks for the info.
good to see it is actually "out-of-my-hands".
I can update / make changes in urllib3 and other packages I include.
But not possible to fix built-in libraries.

So ill just keep with older version of urlllib3 that doesnt try to use https proxies