yt-dlp: [Vimeo] HTTP Error 403 Forbidden / HTTP Error 429 Too Many Requests
DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
- I understand that I will be blocked if I intentionally remove or skip any mandatory* field
Checklist
- I’m reporting that yt-dlp is broken on a supported site
- I’ve verified that I have updated yt-dlp to nightly or master (update instructions)
- I’ve checked that all provided URLs are playable in a browser with the same IP and same login details
- I’ve checked that all URLs and arguments with special characters are properly quoted or escaped
- I’ve searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
- I’ve read the guidelines for opening an issue
- I’ve read about sharing account credentials and I’m willing to share it if required
Region
Europe
Provide a description that is worded well enough to be understood
Downloading the provided link on the Vimeo platform fails.
Provide verbose output that clearly demonstrates the problem
- Run your yt-dlp command with -vU flag added (
yt-dlp -vU <your command line>) - If using API, add
'verbose': TruetoYoutubeDLparams instead - Copy the WHOLE output (starting with
[debug] Command-line config) and insert it below
Complete Verbose Output
[debug] Command-line config: ['-v', '--no-check-certificates', '--no-warnings', '--geo-bypass', 'https://vimeo.com/324146324']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version nightly@2024.06.30.232744 from yt-dlp/yt-dlp-nightly-builds [24f3097ea] (darwin_legacy_exe)
[debug] Python 3.10.5 (CPython x86_64 64bit) - macOS-10.9.5-x86_64-i386-64bit (OpenSSL 1.1.1n 15 Mar 2022)
[debug] exe versions: ffmpeg N-101508-ge93403b (setts), ffprobe N-101508-ge93403b
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.06.02, mutagen-1.47.0, requests-2.32.3, sqlite3-3.37.2, urllib3-2.2.2, websockets-12.0
[debug] Proxy map: {'https': 'localhost:3128'}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1824 extractors
[vimeo] Extracting URL: https://vimeo.com/324146324
[vimeo] 324146324: Downloading webpage
ERROR: [vimeo] 324146324: Unable to download webpage: HTTP Error 403: Forbidden (caused by <HTTPError 403: Forbidden>)
File "yt_dlp/extractor/common.py", line 740, in extract
File "yt_dlp/extractor/vimeo.py", line 834, in _real_extract
File "yt_dlp/extractor/common.py", line 960, in _download_webpage_handle
File "yt_dlp/extractor/common.py", line 909, in _request_webpage
File "yt_dlp/extractor/common.py", line 896, in _request_webpage
File "yt_dlp/YoutubeDL.py", line 4141, in urlopen
File "yt_dlp/networking/common.py", line 117, in send
File "yt_dlp/networking/_helper.py", line 208, in wrapper
File "yt_dlp/networking/common.py", line 337, in send
File "yt_dlp/networking/_requests.py", line 361, in _send
yt_dlp.networking.exceptions.HTTPError: HTTP Error 403: Forbidden
A different configuration:
[debug] Command-line config: ['--proxy', 'localhost:3128', '--no-check-certificates', '--no-warnings', '--geo-bypass', '--force-overwrites', '--write-subs', '-sub-langs', '(en|ru)-orig,en', '--convert-subs', 'srt', '-S', 'res:1080', '-v', 'https://vimeo.com/324146324']
Type account password and press [Return]:
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- [ie/vimeo] Support browser impersonation (#10327) Closes #10325 Authored by: bashonly — committed to wangshaojie1995/yt-dlp by bashonly 2 years ago
It didn’t take much for me to notice these “key points” either. The problem is how to get it working from my AppleScript scripts. You saw three large logs containing manifestations of some obstruction when proxied traffic does not pass via a secure connection. However, the obstruction goes when I discard the original configuration but only in the shell. The decision-making revolves around telling it to run in the AppleScript environment. What would you suggest without resorting to guesswork?
According to the developer of the Squid-based implementation of the proxy in question, that is running in my system, it encodes old-type protocol requests that my system sends out with the newest one. So, I must use it to talk to the world, including Unix binaries that support proxying.
This is due to TLS fingerprinting anti-bot protection. Passing
--impersonate chrome(if curl_cffi is available) or downgrading the URL tohttp://works around the issue.