-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
[Tiktok] Unable to download webpage: 'An existing connection was forcibly closed by the remote host' #30546
Comments
Thank you so much, sir! I saw that fork in the past, but I am happy to hear a confirmation from you. Hope to see porting of that logic to the original repository.
|
From my experience this error is related to https requests on Windows. Never experienced it on POSIX. |
Tried, unfortunately did not work for me. On Ubuntu it hangs on '[TikTok] Setting up session'. |
What about |
you can also download the video if you have an browser add-on |
a) as the log shows, it uses the same tactic as yt-dlp: see #30538 (comment); |
Tried both ways, same error. |
Thank you sir, it works and is very FAST. |
From discussions elsewhere, HTTP/2 may be the discriminator that TT is using. According to the Go |
How do you get this to work? The author barely provided instruction on how to use it. |
They specifically said in the description that they only help patreon/paid users. |
Where else? Do you expect me to pay them if I instantly use their stuff? That is unfair |
Thank you very much for the repo. |
Checklist
Verbose log
Description
Tiktok parsing fails every time with "Unable to download webpage: [WinError 10054] An existing connection was forcibly closed by the remote host" error. I tried with different video URLs and also from different countries. The latest official build was used.
There was a similar problem in the past (Issue 10084), one of the top developers investigated it but had to close because it did not reproduce. It'd be good to check it the same way now, since the call stack is identical. In the past the problem was with a different site, and now it seems to be 100% reproducible.
The text was updated successfully, but these errors were encountered: