Closed MarqFJA87 closed 1 week ago
The sleep-429
option introduced in 1.27.0 interferes here
and skeb itself changed how it sets the needed request_key
cookie.
-o sleep-429=0
and providing the request_key
cookie from your web browser might work until this is fixed.
Tried that. Now I'm getting a slightly different error, and it just terminates afterwards.
[gallery-dl][debug] Version 1.27.0
[gallery-dl][debug] Python 3.10.0 - Windows-10-10.0.19045-SP0
[gallery-dl][debug] requests 2.32.2 - urllib3 2.2.1
[gallery-dl][debug] Configuration Files ['%USERPROFILE%\\gallery-dl\\config.json']
[gallery-dl][debug] Starting DownloadJob for 'https://skeb.jp/@monobe_yuri/works/549'
[skeb][debug] Using SkebPostExtractor for 'https://skeb.jp/@monobe_yuri/works/549'
[urllib3.connectionpool][debug] Starting new HTTPS connection (1): skeb.jp:443
[urllib3.connectionpool][debug] https://skeb.jp:443 "GET /api/users/monobe_yuri/works/549 HTTP/1.1" 429 1601
[skeb][error] HttpError: '429 ' for 'https://skeb.jp/api/users/monobe_yuri/works/549'
gallery-dl.exe https://skeb.jp/@takunomi_athome/works/22 -v
[gallery-dl][debug] Version 1.27.1-dev:2024.06.12 - Executable (dev/windows_x86)
[gallery-dl][debug] Python 3.8.10 - Windows-10-10.0.18363-SP0
[gallery-dl][debug] requests 2.31.0 - urllib3 2.2.1
[gallery-dl][debug] Configuration Files ['E:\\Software\\gallery-dl\\gallery-dl.conf']
[gallery-dl][debug] Starting DownloadJob for 'https://skeb.jp/@takunomi_athome/works/22'
[skeb][debug] Using SkebPostExtractor for 'https://skeb.jp/@takunomi_athome/works/22'
[skeb][debug] Loading cookies from 'E:/Software/gallery-dl/cookies.txt'
[urllib3.connectionpool][debug] Starting new HTTPS connection (1): skeb.jp:443
[urllib3.connectionpool][debug] https://skeb.jp:443 "GET /api/users/takunomi_athome/works/22 HTTP/1.1" 429 1601
[skeb][error] HttpError: '429 ' for 'https://skeb.jp/api/users/takunomi_athome/works/22'
Fixed in 11421cf940234231f10520b3be60bd18df7e2637
Fixed my issue, thanks!
HOW TO USE SKEB,PY
Woke up to find that I can't download from Skeb anymore due to a "429 Too Many Requests" error. Here's an example log (the link is NSFW).
It just keeps on looping from then on, as when the stated time is reached, the exact same error is returned and a new time is given, repeat ad infinitum.