yt-dlp: [Vimeo] HTTP Error 429/403 When Using Impersonate Target

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

Region

Australia

Provide a description that is worded well enough to be understood

I am downloading videos from a page that embeds Vimeo videos. I was able to download successfully until a few minutes ago. Now, when I use the same command that I have been using all along, I get the error:

Got HTTP Error 429 when using impersonate target "chrome-110:windows-10". If you are using a data center IP or VPN/proxy, your IP may be blocked; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U

Has my IP been blocked by Vimeo? I have downloaded about 10-15 videos in the last 48 hours. I am able to normally access the webpage that embeds these videos on Chrome, and play these videos.

I would really appreciate any help or advice as I really want to download these videos. Thank you!

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': True to YoutubeDL params instead
  • Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output

[debug] Command-line config: ['-vU', '-F', '--referer', 'https://www.jkyog.org/portal/spiritual-retreat-family-camp', 'https://player.vimeo.com/video/971555691']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version stable@2024.07.09 from yt-dlp/yt-dlp [7ead7332a] (pip)
[debug] Python 3.12.4 (CPython arm64 64bit) - macOS-14.5-arm64-arm-64bit (OpenSSL 3.3.1 4 Jun 2024)
[debug] exe versions: ffmpeg 7.0.1 (setts), ffprobe 7.0.1
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.07.04, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.46.0, urllib3-2.2.2, websockets-12.0
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1834 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: stable@2024.07.09 from yt-dlp/yt-dlp
yt-dlp is up to date (stable@2024.07.09 from yt-dlp/yt-dlp)
[vimeo] Extracting URL: https://player.vimeo.com/video/971555691
[vimeo] 971555691: Downloading webpage
ERROR: [vimeo] 971555691: Got HTTP Error 429 when using impersonate target "chrome-110:windows-10". If you are using a data center IP or VPN/proxy, your IP may be blocked; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "/Users/username-hidden/.local/pipx/venvs/yt-dlp/lib/python3.12/site-packages/yt_dlp/extractor/common.py", line 740, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/username-hidden/.local/pipx/venvs/yt-dlp/lib/python3.12/site-packages/yt_dlp/extractor/vimeo.py", line 859, in _real_extract
    raise ExtractorError(

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 6
  • Comments: 66 (17 by maintainers)

Most upvoted comments

I found a solution for my missing private vimeo IDs. What I get: if I use “player.vimeo.com/video/VIMEOID1” I get HTTP Error 401: Unauthorized (caused by <HTTPError 401: Unauthorized>) if I use “vimeo.com/VIMEOID1” on the same ID, I get Got HTTP Error 429 when using impersonate target “chrome-110:windows-10”. If you are using a data center IP or VPN/proxy, your IP may be blocked; After that I open vimeo.com/VIMEOID1 in a incognito chrome browser and I see the capture. the forwarding leads to nowhere, because the video ID is private. After that I can download from “player.vimeo.com/video/VIMEOID1” For the next ID I need to close and reopen incognito Chrome. After I browsed to vimeo.com/VIMEOID2 it works with yt-dlp downloading from “player.vimeo.com/video/VIMEOID2”

[vimeo] XXXXXXXXX: Got HTTP Error 403 when using impersonate target "chrome-110:windows-10". If you are using a data center IP or VPN/proxy, your IP may be blocked; please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U

I’m trying to download about two dozen videos from Vimeo. I get this 403 error seemingly more often when I use yt-dlp 'vimeo.com/xxxxxxxx' --recode mp4 but I’m getting it frequently when just using yt-dlp 'vimeo.com/xxxxxxxxx' as well.

I’m not entirely sure what to tell you. Select the iframe context and you should have the playerConfig available. image Alternatively, look at the network tab.

This guy managed to fix the issue: https://github.com/limontec/vm-video-downloader Any chance to get it implemented on yt-dlp?

@rafaelfndev It sounds like you’re not using the --referer flag in yt-dlp when downloading a private video. Personally I cannot download a private video without this flag.

It worked!

yt-dlp --referer https://example.com/allowed-website-referer https://player.vimeo.com/video/833019403

On closer inspection, it was a noob mistake 🤦‍♀️. I’m using the lib node-website-scraper to clone entire website, and I do several validations and pass several parameters to node-website-scraper before calling yt-dlp. So after I saved the entire website, I forgot that the parameters passed to node-website-scraper are not passed to yt-dlp (my big mistake), so it didn’t work.

Thanks for shedding some light on this.

@rafaelfndev It sounds like you’re not using the --referer flag in yt-dlp when downloading a private video. Personally I cannot download a private video without this flag.

If you’re getting 403/429/401 errors with curl-cffi/impersonation, there is no fix for that yet. There is no known solution yet

I found a fix - for now!

I started getting the 429 error a few days ago, basically everytime I tried. However I found a fix: it appears that if you have the same URL open with active playback, in any browser, the error doesn’t show up.

Beware you have to keep the video playing until the download if finished, otherwise it will start timing out.

Hope it helps someone else while the DEVs manage to fix the issue - if it’s possible at all. BTW thanks for this awesome piece of sofwrare! Cheers!

That did indeed work for me! It was my first ever attempt to use yt-dlp, and I didn’t know if I was doing anything wrong, but seems like Vimeo started detecting the yt-dlp traffic. But parallel to playing in the browser works!

I found a fix - for now!

I started getting the 429 error a few days ago, basically everytime I tried. However I found a fix: it appears that if you have the same URL open with active playback, in any browser, the error doesn’t show up. Beware you have to keep the video playing until the download if finished, otherwise it will start timing out. Hope it helps someone else while the DEVs manage to fix the issue - if it’s possible at all. BTW thanks for this awesome piece of sofwrare! Cheers!

Not working for me. I try to download private video which is embedded to a website, where I have paid access to the content. Even when the video is running same ID gets 429. What I can say: my list of non working IDs gets shorter and shorter day by day. Each day I try to download them. Most get 429 (I use imersonate=safari) and fault says target “chrome-110:windows-10”. But some start to download. no parallel downloads, 1Sec delay between attempts

I did it by right-clicking on the Vimeo Frame, than from the menu > view Frame source, than in the source code you find the player embed URL. If you open that link in another tab, it should play the video. While this video is playing, it works for me.

JFYI, what @coletdjnz said has been the case for at least months. I had a personal project to scrape some vimeo metadata from webpages and have noticed that for a while.

You usually trigger the captcha by having too many threads (>10, or even fewer if your Internet is fast). After solving it your reputation would be raised back to normal until you did the same thing again. Repeatedly doing so would got your IP blocked “permanently” (not actually permanent usually).