# Outdated SSL/Python? Handshake errors

**URL:** <https://forums.plex.tv/t/outdated-ssl-python-handshake-errors/155119>\
**Category:** Dev/API Corner\
**Tags:** plugin-dev\
**Created:** [August 19, 2016, 11:02am UTC](https://forums.plex.tv/t/outdated-ssl-python-handshake-errors/155119 "2016-08-19T11:02:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![JeppeTh](https://avatars.discourse-cdn.com/v4/letter/j/b5ac83/32.png) [@JeppeTh](https://forums.plex.tv/u/JeppeTh)\
**Post date:** [August 19, 2016, 11:02am UTC](https://forums.plex.tv/t/outdated-ssl-python-handshake-errors/155119/1 "2016-08-19T11:02:38Z")

</div>

Hi!

I have ssl handshake problems on my Viaplay plugin - [https://forums.plex.tv/discussion/82378/rel-viaplay-se-no-dk-fi#latest](https://forums.plex.tv/discussion/82378/rel-viaplay-se-no-dk-fi#latest).  
I noticed that some “Vice” plugin had the same issue.

On my local python installation the “python request module” managed to handle the handshake properly.

I tried to import this in my channel, but it failed due to ancient ssl version etc:

> <https://github.com/requests/requests/issues/2735>

Does anyone know how to get around this?

Is Plex FW planning some update of python/ssl versions?

I guess there’s a risk that more and more channels bump into similar issues. So some general FW solution should be preferred.

Br  
Jesper

---

<div class="post-metadata">

**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\
**Post date:** [August 19, 2016, 8:35pm UTC](https://forums.plex.tv/t/outdated-ssl-python-handshake-errors/155119/2 "2016-08-19T20:35:53Z")

</div>

Hi Jeppe.

This is already been tracked by Plex, but what the outcome will be, is sadly unknown to me, as well as an ETA on this.

But on their Radar

/T

---

<div class="post-metadata">

**Author:** ![JeppeTh](https://avatars.discourse-cdn.com/v4/letter/j/b5ac83/32.png) [@JeppeTh](https://forums.plex.tv/u/JeppeTh)\
**Post date:** [August 19, 2016, 9:40pm UTC](https://forums.plex.tv/t/outdated-ssl-python-handshake-errors/155119/3 "2016-08-19T21:40:18Z")

</div>

> @dane22 said:  
> Hi Jeppe.
> 
> This is already been tracked by Plex, but what the outcome will be, is sadly unknown to me, as well as an ETA on this.
> 
> But on their Radar
> 
> /T  
> Is there some other thread about this and its possible progress?

---

<div class="post-metadata">

**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\
**Post date:** [August 19, 2016, 9:52pm UTC](https://forums.plex.tv/t/outdated-ssl-python-handshake-errors/155119/4 "2016-08-19T21:52:39Z")

</div>

Only avail to Plex employees.  
Even Ninja’s have no access ☹

---

<div class="post-metadata">

**Author:** ![JeppeTh](https://avatars.discourse-cdn.com/v4/letter/j/b5ac83/32.png) [@JeppeTh](https://forums.plex.tv/u/JeppeTh)\
**Post date:** [August 19, 2016, 10:01pm UTC](https://forums.plex.tv/t/outdated-ssl-python-handshake-errors/155119/5 "2016-08-19T22:01:43Z")

</div>

> @dane22 said:  
> Only avail to Plex employees.  
> Even Ninja’s have no access ☹

So there’s a leak? Since you seem to know about it…  
😃

---

<div class="post-metadata">

**Author:** ![dane22](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dane22/32/4389_2.png) [@dane22](https://forums.plex.tv/u/dane22)\
**Post date:** [August 19, 2016, 10:12pm UTC](https://forums.plex.tv/t/outdated-ssl-python-handshake-errors/155119/6 "2016-08-19T22:12:05Z")

</div>

I’m a Ninja, and as such, can ask people you can’t 😛

But even Ninja info is limited, since as you know, Plex never ever hands out roadmaps nor ETA’s

/T

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [January 8, 2020, 7:59pm UTC](https://forums.plex.tv/t/outdated-ssl-python-handshake-errors/155119/7 "2020-01-08T19:59:12Z")

</div>


