Open tomontherun opened 10 years ago
The 188.21.9.* servers look like valid YouTube servers, they're just on the premises of Telekom Austria. Can you describe that network a little bit more? Is it mobile? Is it a corporate network where a transparent proxy could be in between all traffic? In any case, it looks like the remote end is misconfigured to not support SSL (we always pick HTTPS for all intermediate URLs).
Can you post the output you get when you surf to http://youtube.com:443/ (or, if you're technically inclined: what do you get for curl -i http://www.youtube.com:443/
)? That should generate an error, but my guess is that whatever is meddling with the connection is always speaking HTTP, even on port 443. What does your webbrowser say when you surf to https://youtube.com/ ?
We'll consider adding a switch to prefer HTTP over HTTPS, but what you're seeing is really the fault of the proxy.
Thanks for your comment. Telekom Austria is the provider in this case (it's a normal DSL connection), but the 188.31.9.* servers are also returned if I ask the Google DNS server (8.8.8.8) so they seem to be the official youtube servers for this network/area.
curl -vi http://www.youtube.com:443
* About to connect() to www.youtube.com port 443 (#0)
* Trying 188.21.9.52... connected
* Connected to www.youtube.com (188.21.9.52) port 443 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.15 libssh2/1.2.6
> Host: www.youtube.com:443
> Accept: */*
>
* Empty reply from server
* Connection #0 to host www.youtube.com left intact
curl: (52) Empty reply from server
* Closing connection #0
Also gives me an error in the browser. https://www.youtube.com works fine.
I will probably meddle with my DNS server to return a different IP for Youtube.
This is probably a dupe of https://github.com/rg3/youtube-dl/issues/2219
Try upgrading your Python.
Hi, there seems to be a problem with ssl on some youtube servers. Test command:
python youtube-dl -vv -f 137+140 https://www.youtube.com/watch?v=eDeKetrM5Wc
In country A this gives me:
But works perfectly fine in country B on an identical system.
DNS Lookup country A:
DNS Lookup country B:
It doesn't make any difference if I use the video link with https or http. Any ideas? Thanks