On Fri, 23 Nov 2018, Olof Johansson wrote:
> On 18-11-19 18:37 +0100, Cristian Ionescu-Idbohrn wrote:
> > This is what I see:
> ...
> > requests.exceptions.SSLError:
> > HTTPSConnectionPool(host='streaming-loadbalancer.ur.se', port=443): Max
> > retries exceeded with url: /loadbalancer.json (Caused by
> > SSLError(SSLError("bad handshake: Error([('SSL routines',
> > 'ssl_choose_client_version', 'unsupported protocol')],)",),))
> >
> > when trying to download:
> >
> > https://urplay.se/program/204949-roster-fran-australiens-aboriginer
> >
> > for example. Works fine when playing it in chromium, though.
> >
> > Downloading from svtplay.se works fine, though.
>
> Thanks for the report, I have been postponing upgrading to the
> new 2.0+ version, but should get on that asap. Hopefully that
> should solve it.
Now that 2.1-1 is available in unstable, I tested. The problem
persists :(
Checked using https://www.ssllabs.com/ssltest/analyze.html.
urplay.se (212.116.95.198, 212.116.95.234, etc.) seems ok (supports
TLS 1.2).
It redirects to streaming-loadbalancer.ur.se/loadbalancer.json
(130.242.59.74), which seems to be _the real problem_ (supports _only_
TLS 1.0/SSL3). loadbalancer.json is just one line (with no line
terminators):
{"geoip_country_code":"SE","redirect":"streaming4.ur.se"}
It redirects to streaming4.ur.se (130.242.59.77), which also seems to
be ok (supports TLS 1.2).
I wonder if this could be worked around, as it must affect all
python3 based svtplay-dl, AFAICU. Please forward upstream.
Cheers,
--
Cristian
