-
Notifications
You must be signed in to change notification settings - Fork 6
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
Inability to process request #7
Comments
This very long exception chain should give us some context:
Do you think that this may be TLS handshake fingerprinting? |
I'll see if turning off HTTPS/cert checking works. Not a big fan of this, but it seems we're left with no choice. |
Yeah, that didn't work. Related ongoing yt-dlp issue: yt-dlp/yt-dlp#3776 A youtube-dl patch fixes it via the old @BritishBenji Do you want to wait for yt-dlp to figure this out, or wait on me (3-6 days) to figure this out? |
I'll have a look over it and see what I can do tomorrow in terms of this repo specifically (if I can do anything), it's nearly 2am for me at the moment, so I'm unsure if there's any fixes that could be in place for this without relying on yt-dlp's PR. Otherwise, I'm more than happy to wait for yt-dlp to merge the PR, don't worry about it too much, I currently have the free time to do what this repo does for me by hand so it's not a massive issue |
Update: situation has gotten more complicated: yt-dlp/yt-dlp#3776 (comment). I'm glad I didn't bother implementing the yt-dl fix, as it's now broken. The solution apparently is https://github.com/kjerk/yt-dlp/commit/de4a6005e70f81f0f88807a368895a6da852a24b, but I don't completely get it and it's apparently not preferred. |
Wow, even I get hit with a captcha when I simply try to navigate to a channel page in my browser. They're really cracking down. Guess we'll continue waiting. |
It works again! I won by doing absolutely nothing! |
I can't find a clear error, but when running viewing the debug logs, all I find is:
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (3): www.tiktok.com:443
Until eventually the webpage results in a timeout
The text was updated successfully, but these errors were encountered: