-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
afreecatv: SSLV3_ALERT_HANDSHAKE_FAILURE #8187
Comments
See #2043 for related previous discussion I would say that's expected, however.. pukkandan's comment at the time:
This is possible to implement now per request with the new networking framework, if this is a common problem with the extractor/site. Edit: though, I'm not sure why this is happening. We enforce the same set of ciphers and tls version for openssl 1.1.1+, and I can't repro |
This is happening to me now, tried different machines (from a VPS) which also has the previous yt-dlp version, same result.
Tried --legacy-server-connect same result. |
@jouven strange, for me using
Without it I get the same error as you! But my OpenSSL library is older than yours... |
I tried again today and in my up to date desktop setup, arch btw, now it works with or without |
@jouven maybe it is linked with the Python version?.. If you want you can post your log with |
It seems to be an API server issue with AfreecaTV. I can reproduce it with the following command. curl -v --tlsv1.2 --ciphers '@SECLEVEL=2:ECDH+AESGCM:ECDH+CHACHA20:ECDH+AES:DHE+AES:!aNULL:!eNULL:!aDSS:!SHA1:!AESCCM' "https://api.m.afreecatv.com" In short, the reason is that the API server still uses SHA1. yt-dlp/yt_dlp/networking/_helper.py Lines 154 to 156 in add96eb
According to the above rules, only the following ciphers are supported: OpenSSL supported cipher list
However, the API server only supports the following ciphers: API server cipher list
So it looks like the error is occurring because there is no cipher supported by OpenSSL when connecting to the API server. |
I found a very simple solution: downgrading to HTTP solves the problem. 😂 |
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
Checklist
Region
Korea
Provide a description that is worded well enough to be understood
Using '--legacy-server-connect' works.
Provide verbose output that clearly demonstrates the problem
yt-dlp -vU <your command line>
)'verbose': True
toYoutubeDL
params instead[debug] Command-line config
) and insert it belowComplete Verbose Output
The text was updated successfully, but these errors were encountered: