You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've checked that the site i'm trying to download from is in the Supported Sites list from yt-dlp
I understand that the issue will be (ignored/closed) if I intentionally remove or skip any mandatory field.
Describe the bug
I'm trying to download some videos and audio for my editing purposes but whenever I press the "download" button seal processes for some time and says "we couldn't fetch the video" and it had happened before too and this is too much now I want some exact solution for this
URL: https://youtube.com/watch?v=XyDsjxs8Y7c&si=MgN6TZ0_wJlCKhTK
WARNING: [youtube] Unable to download webpage: [Errno 7] No address associated with hostname
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (1/3)...
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (2/3)...
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (3/3)...
WARNING: [youtube] Unable to download API page: [Errno 7] No address associated with hostname (caused by TransportError('[Errno 7] No address associated with hostname'))
WARNING: [youtube] Unable to download webpage: [Errno 7] No address associated with hostname
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (1/3)...
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (2/3)...
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (3/3)...
WARNING: [youtube] Unable to download API page: [Errno 7] No address associated with hostname (caused by TransportError('[Errno 7] No address associated with hostname'))
ERROR: [youtube] XyDsjxs8Y7c: Failed to extract any player response; 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
Screenshots & Screen Records
Additional context
No response
The text was updated successfully, but these errors were encountered:
Checklist
Describe the bug
I'm trying to download some videos and audio for my editing purposes but whenever I press the "download" button seal processes for some time and says "we couldn't fetch the video" and it had happened before too and this is too much now I want some exact solution for this
To Reproduce
No response
Error reports
App version: 1.13.0 (11302)
Device information: Android 11 (API 30)
Supported ABIs: [arm64-v8a, armeabi-v7a, armeabi]
Yt-dlp version: 2024.09.07.232731
URL: https://youtube.com/watch?v=XyDsjxs8Y7c&si=MgN6TZ0_wJlCKhTK
WARNING: [youtube] Unable to download webpage: [Errno 7] No address associated with hostname
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (1/3)...
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (2/3)...
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (3/3)...
WARNING: [youtube] Unable to download API page: [Errno 7] No address associated with hostname (caused by TransportError('[Errno 7] No address associated with hostname'))
WARNING: [youtube] Unable to download webpage: [Errno 7] No address associated with hostname
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (1/3)...
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (2/3)...
WARNING: [youtube] [Errno 7] No address associated with hostname. Retrying (3/3)...
WARNING: [youtube] Unable to download API page: [Errno 7] No address associated with hostname (caused by TransportError('[Errno 7] No address associated with hostname'))
ERROR: [youtube] XyDsjxs8Y7c: Failed to extract any player response; 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
Screenshots & Screen Records
Additional context
No response
The text was updated successfully, but these errors were encountered: