-
-
Notifications
You must be signed in to change notification settings - Fork 951
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
HTTP request failed: 418 #431
Comments
oh i dont know it supported weibo now, but when i'm testing with archive enabled, everything worked, no problem at all |
i used it yesterday and it worked fine, it started resuming downloads right after checking the exsiting ones, today the folder got over 5000 files, it feels like it's getting overwhelmed while checking?? |
The 418 HTTP status code is Weibo's way of saying "You are overusing our API". I don't know why they aren't using the default The problem now is resuming your download from were it left off. With the way things work at the moment, gallery-dl will always start at the beginning, skip over already downloaded files, and will eventually fail with the same error because it sent too many API requests in too short of a time while trying to get to where it previously was. The only way would be to manually modify the start page in the source code itself: gallery-dl/gallery_dl/extractor/weibo.py Line 99 in 20eb6c4
Maybe a |
i'm using this https://github.com/nondanee/weiboPicDownloader with simultaneous download set to 2. maybe you can take a look. |
when i set a range value it shows me the error immidiatly without even checking for existing files, but i did an attempt with a lower value on range and it did skip and searched untill it crashed.
thanks will do |
here is how i made it work. |
i'm using the --download-archive FILE command, so it starts checking the existing files but it stops halfway and it shows me this error:
[weibo][error] HTTP request failed: 418: for url: https://m.weibo.cn/api/container/getIndex
The text was updated successfully, but these errors were encountered: