READ THIS BEFORE OPENING A NEW ISSUE! THIS MEANS YOU!

[dirkf]

The 2021.12.17 release linked in the download instructions is now effectively obsolete; in particular, it does not generally work with YouTube itself. Before raising an issue, try a nightly release build. But if you still need to raise an issue ...

Please log in to GitHub before using the 'New Issue' button.

Although 'New Issue' makes you log in, GitHub doesn't then show the template chooser that we set up to help you report issues. If you log in before using 'New Issue', you are correctly redirected to the chooser.

The chooser is here. But read on, really.

If you raise an issue without using the chooser, or if you ignore or misuse the chosen template, your issue is likely either to be a duplicate of an issue that is already being handled, or to lack sufficient supporting information to solve the problem. Maintainers may close such issues without prejudice.

If your problem occurred when running another package that invokes youtube-dl, try to reproduce the problem with a youtube-dl ... command, or report it through the support channel for the other package; similarly if the problem occurred when running your own code.

If you are reporting an error with diagnostic output like this

youtube_dl...SomeError: oops; please report this issue on https://yt-dl.org/bug ...

do follow the instructions there, including, implicitly, this post.

• Take note of the error message, oops in the example above.
• The issue template will ask you to check for an existing issue that covers the error (but first review 'Known issues' below):
  • use something like is:issue oops -label:duplicate in the search field of the project issue tracker, where oops is the message that you noted before;
  • add -in:title if the search returns too many results.
• HTTP errors 4xx and 5xx and errors in data extraction are likely to be specific to a single site or extractor: for such errors, prioritise issues that match the site or extractor in your problem.
• Don't raise a new issue if an existing issue matches your problem.
• Why is all this important for the project?
• Some German madness is temporarily breaking the domain yt-dl.org: until the name points to a valid domain, there is a revised version of the README (and the reporting URL is this tracker, but you're already here).

If you were actually running yt-dlp, go there. Similarly with other forks, unless code clearly matches the _youtubedl release or git master code.

If your problem concerns HTTP Error 429: Too Many Requests, especially with YouTube or a video hosted there, read #23638 and its linked issue first to avoid having your issue closed immediately.

Although your issue may concern a site that uses a language other than English and/or English may not be your first language, please formulate your issue in English. Various online translation tools are available to help you, even this. By all means include your original text in case the automatic translation is defective.

As here, you can use the HTML <details> element to hide some original text, or to improve readability when posting multiple logs, etc.

Like this: ```

Original text

original text or other details here

``` Use `...` instead of \`...\` in the summary text.

Known issues, fixed in git master code, or update/install from the nightly release repo (further installation guidance):

• YouTube: Unable to extract nsig jsi ...
• YouTube: Error 403 when downloading ... (check the issue in case your YT 403 problem may be different)
• YouTube: Unable to extract yt initial data on playlist (also a swathe of related errors
• YouTube: Unable to extract uploader id
• YouTube: Unable to decode n-parameter: download likely to be throttled
• Vimeo: Unable to extract info section
• YouTube: shorts URL causes "unable to recognize tab page" errors
• YouTube: youtube-dl does not find videos listed on user/channel "shorts" subpage
• ITVX support: (but new problems have been reported that are not yet resolved)
• YouTube: Signature extraction failed, KeyError QV
• Security: File Downloader cookie leak.

[dirkf]

The mentioned GH issue creation bug might be worked around if every project used a new format for the templates. Or GH could have actually fixed it once.