Could not fetch video info

[YogTandel]

Checklist

• [X] I'm reporting a bug unrelated to a specific site.
• [X] I've verified that I'm running the latest version of yt-dlp.
• [X] I've verified that I'm running the latest stable version of Seal or any later preview versions.
• [X] I've read the Contributing guidelines and Code Of Conduct.
• [X] I've checked that the site i'm trying to download from is in the Supported Sites list from yt-dlp
• [X] I understand that the issue will be (ignored/closed) if I intentionally remove or skip any mandatory field.

Describe the bug

I didn't able to download Instagram reels for all reels it shows this same error

To Reproduce

No response

Error reports

App version: 1.13.0 (11302) Device information: Android 14 (API 34) Supported ABIs: [arm64-v8a, armeabi-v7a, armeabi] Yt-dlp version: 2024.09.27.232842

URL: https://www.instagram.com/reel/DAeRZC4MTJW/?igsh=NW54M2lrMWRsdnYw Deprecated Feature: Support for Python version 3.8 has been deprecated. Please update to Python 3.9 or above WARNING: [Instagram] DAeRZC4MTJW: General metadata extraction failed (some metadata might be missing). WARNING: [Instagram] unable to extract shared data; 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 WARNING: [Instagram] Main webpage is locked behind the login page. Retrying with embed webpage (some metadata might be missing). WARNING: [Instagram] unable to extract additional data; 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 ERROR: [Instagram] DAeRZC4MTJW: Requested content is not available, rate-limit reached or login required. Use --cookies, --cookies-from-browser, --username and --password, --netrc-cmd, or --netrc (instagram) to provide account credentials

Screenshots & Screen Records

Additional context

No response

[github-actions[bot]]

This issue has been closed and labeled as duplicate. Please see issue #1399 for more details. If you believe this is not the case, you can reopen this issue.