node-ytdl-core icon indicating copy to clipboard operation
node-ytdl-core copied to clipboard

MinigetError: Status code: 410 at ClientRequest.

Open AbubakarZorrain opened this issue 3 years ago • 13 comments

Before creating an issue, please try the following

  • Are you on the latest version of ytdl-core?
    • To check, run npm ls ytdl-core
    • If you're using a bot or application that depends on ytdl-core, look at the bottom of the readme on how to update the library
    • Otherwise, if you're directly importing ytdl-core, to install the latest version, run npm install ytdl-core@latest
  • Search the list of issues for a possible duplicate.
    • If there is a duplicate issue thread, but it's closed, only post in it if it's been active in the past month. Otherwise, creating a new issue thread is fine.
  • If your question is about using the library for a specific use case, check out the examples folder.

Otherwise, feel free to open an issue

Include the following if your issue is a bug

  • If you're getting a specific error message, include the full stack trace
  • If you're getting unexpected behavior without an error message
    • What should happen?
    • What happens instead?
  • Include any relevant code around ytdl-core. You don't have to upload your entire program, small snippets are fine.
  • If this error happens only on some videos, include a link or links to videos.

AbubakarZorrain avatar Aug 29 '22 16:08 AbubakarZorrain

Guys I am getting this error, whichone operation I start from this module. Info-get, download, trim etc....

AbubakarZorrain avatar Aug 29 '22 16:08 AbubakarZorrain

@maxogden @edef1c @R4wizard @sesam

AbubakarZorrain avatar Aug 30 '22 06:08 AbubakarZorrain

@TimeForANinja Is there any solution for this issue? Please recommend.

AbubakarZorrain avatar Sep 04 '22 11:09 AbubakarZorrain

Please anyone slove the issue

cutdown avatar Sep 06 '22 14:09 cutdown

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Nov 12 '22 12:11 stale[bot]

This issue was not sloved. I getti' same error. I think it has something to do with the video data. If someone gettin' a similar error, I suggest DM me or send it here (if this is allowed here at all) so that I can study the video and identify a pattern

gohellp avatar Dec 01 '22 01:12 gohellp

I am getting the same errors in these videos: Not existing video: https://www.youtube.com/watch?v=FmqZpNj3n_U Existing video: https://www.youtube.com/watch?v=nlbmkjdaz_c

jinpeng0102 avatar Dec 23 '22 15:12 jinpeng0102

yea i'm running into it too... https://www.youtube.com/watch?v=LqB9olSAu90

"video unavailable"... it's in a playlist of mine and the youtube api still returns it with the playlist even though its no longer available...

i just wish there was a way to catch the error... instead it crashes the node server...

AaronMeyers avatar Dec 29 '22 05:12 AaronMeyers

I don't understand how this issue is still not resolved. I guess its quite difficult to fix. I have gone through most of the closed issues with this status code and none of the solutions have worked. I'll mention all the ones I have gone through, some people on there mentioned that it worked for them so try all these. If it doesn't work then you are probably going to have to find your own solution. #1009, #1080, #1090. Also TimeForANinja mentioned that its a problem without a real fix: https://github.com/fent/node-ytdl-core/issues/1067#issuecomment-1059602473

Edit: The reason why you are getting the error in the first place is because of restricted videos or non existent videos. Examples: https://www.youtube.com/watch?v=W3GrSMYbkBE , https://www.youtube.com/watch?v=FmqZpNj3n_U .

kiri836 avatar Feb 12 '23 11:02 kiri836

Both using cookies and using https://github.com/fent/node-ytdl-core/pull/1080 made a video with a suicide topic warning work for me.

pixelblob avatar Mar 24 '23 00:03 pixelblob

Both using cookies and using #1080 made a video with a suicide topic warning work for me.

At the time that I wrote the comment, #1080 wouldn't even work when tried in the browser. I tested it a few minutes ago in the browser and it seemed to work, so I assume some change occurred on YouTube's that allowed this to work again. This really is just a temporary solution until it breaks again; a real solution needs to be found.

I doubt having the cookies actually does anything, I messed around with cookies quite a bit when I was still trying to solve the issue and they did absolutely nothing. You should try using #1080 without the cookies, and also try doing cookies only. I am assuming only the former variation will work.

kiri836 avatar Mar 24 '23 01:03 kiri836

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Jun 18 '23 13:06 stale[bot]