Node-ytdl-core: Error: Too many redirects (from miniget used by ytdl-core)

Created on 28 Aug 2017 · 31Comments · Source: fent/node-ytdl-core

2|Senpai   | Error: Too many redirects
2|Senpai   |     at ClientRequest.<anonymous> (/root/Senpai-Bot/Senpai-Bot-Discord/node_modules/miniget/lib/index.js:59:19)
2|Senpai   |     at Object.onceWrapper (events.js:316:30)
2|Senpai   |     at emitOne (events.js:115:13)
2|Senpai   |     at ClientRequest.emit (events.js:210:7)
2|Senpai   |     at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:565:21)
2|Senpai   |     at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23)
2|Senpai   |     at TLSSocket.socketOnData (_http_client.js:454:20)
2|Senpai   |     at emitOne (events.js:115:13)
2|Senpai   |     at TLSSocket.emit (events.js:210:7)
2|Senpai   |     at addChunk (_stream_readable.js:266:12)
2|Senpai   |     at readableAddChunk (_stream_readable.js:253:11)
2|Senpai   |     at TLSSocket.Readable.push (_stream_readable.js:211:10)
2|Senpai   |     at TLSWrap.onread (net.js:585:20)

i get this error often in the last time and im not quit sure how to handle properly since i cant catch it property (seems to be thrown in the miniget lib or smth) and maybe you could tell me if its an network issue or something like that

bug

Source

DevYukine

👍8

Most helpful comment

Yeah that's how you ask open source software developers who do this as a hobby in their free time to fix something! Insult them! That seems like a great idea!

FireController1847 on 16 Jul 2019

👍9

All 31 comments

Looks similar to the error from #187, but that one is too many reconnects. So possibly, this is a separate issue.

Do you have an example video where this happens?

fent on 28 Aug 2017

oh not at the moment, i will try to get one ASAP to help you investigate the issue :)

DevYukine on 28 Aug 2017

I got the same while testing, and it appears that if the video does not exist, this happens:
Error: Too many redirects at ClientRequest.<anonymous> (/home/juusolain/CordBot/node_modules/miniget/lib/index.js:59:19) at Object.onceWrapper (events.js:316:30) at emitOne (events.js:115:13) at ClientRequest.emit (events.js:210:7) at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:565:21) at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23) at TLSSocket.socketOnData (_http_client.js:454:20) at emitOne (events.js:115:13) at TLSSocket.emit (events.js:210:7) at addChunk (_stream_readable.js:266:12)
This is probably the same thing

jusola on 10 Sep 2017

oh yea that would make sense since you get redirected if the video was claimed/deleted if i remember correct

DevYukine on 11 Sep 2017

Ahh it's happening still @fent pls fix kthx <3

FireController1847 on 9 Feb 2018

👍4

Yep, still happening sometimes.

arjndr on 6 May 2018

Are there any videos where this consistently happens?

fent on 5 Aug 2018

My unit tests are now failing with this: https://www.youtube.com/watch?v=oVXg7Grp1W8

But I can override them with an environment variable and this worked: https://www.youtube.com/watch?v=OLxY0HDakRk

jimbuck on 15 Jan 2019

It is happening with this video: https://www.youtube.com/watch?v=PimVw0LomLs

Using ytb2mp3:
https://github.com/ytb2mp3/ytb2mp3/issues/2

mandazi on 16 Jan 2019

It is happening with this video: https://www.youtube.com/watch?v=PimVw0LomLs

Ok I'm able to replicate with itag 22 of this. Will investigate.

Using ytb2mp3:
ytb2mp3/ytb2mp3#2

This is using an outdated version of ytdl-core btw. You can see in the package-lock.json file. The error still happens with the video above, but you should always be using the latest version or you might run into other errors.

fent on 18 Jan 2019

👍1

Going to keep this opened to remember to investigate video: https://www.youtube.com/watch?v=PimVw0LomLs

fent on 9 Feb 2019

Any updates on this?

mandazi on 28 Feb 2019

Been on a break for a while, will get back to it in a few weeks.

fent on 1 Mar 2019

This 'Too many redirects' error seems to occur when multiple ytdl calls are being processed at the same time. If i download a single youtube video at a time i never get this, only when i download multiple videos without letting the previous one finish.

ShawnAndrews on 10 Mar 2019

👍1

@ShawnAndrews I have this issue while downloading only one video at the same time

EmerickH on 10 Mar 2019

The same error is also working with me.
Urls:
https://www.youtube.com/watch?v=IbbtAy2jvLM
https://www.youtube.com/watch?v=lwIIODceKyY

Gabriel10Velloso on 12 Mar 2019

yo wtf fix this shit already

suroh001 on 16 Jul 2019

👎15 👀2

Yeah that's how you ask open source software developers who do this as a hobby in their free time to fix something! Insult them! That seems like a great idea!

FireController1847 on 16 Jul 2019

👍9

Any updates on this?

danielboos1 on 3 Sep 2019

👍1

I found out if you requeue the same video and it will actually play, so maybe you can fix it by making it retry on this error

danielboos1 on 21 Sep 2019

Curious if people here are using proxies or not.
It only happens for me when I'm using a proxy.

gdoron on 31 Oct 2019

Curious if people here are using proxies or not.
It only happens for me when I'm using a proxy.

And how you fix it with proxy?

mh4ck on 22 Nov 2019

@mh4ck I didn't.
Had I had the time I would fork ytdl to use request module instead of miniget, it is by far more robust.

gdoron on 23 Nov 2019

we tried to stay away from request since it's a heavyweight at more then 200x the size of miniget

TimeForANinja on 11 Feb 2020

And apparently Request is also "unmaintained" now. I highly recommend Got as an alternative.

jimbuck on 11 Feb 2020

Error: input stream: Too many redirects
at ClientRequest. (/location_dont_matter/node_modules/ytdl-core/node_modules/miniget/dist/index.js:129:42)
at Object.onceWrapper (events.js:417:26)
at ClientRequest.emit (events.js:310:20)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:596:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:119:17)
at HTTPParser.execute ()
at TLSSocket.socketOnData (_http_client.js:469:22)
at TLSSocket.emit (events.js:310:20)
at addChunk (_stream_readable.js:286:12)
at readableAddChunk (_stream_readable.js:268:9)

Nieme on 29 May 2020

I m also facing same error anyone have fix this issue?

nasir03082409229 on 30 May 2020

status update on this issue, I'm unable to download the following video

https://www.youtube.com/watch?v=PimVw0LomLs

however, this time there's no error, the download starts, only downloading around 500kb, then stalls

fent on 30 May 2020

this problem might be caused by the command !serverQueue, try changing the volume to 5 maybe that could help i guess

primeartsXD on 15 Jun 2020

👎1

I had this issue and then it got solved when I went to node_modules>miniget>dist>index.js and changed the value of maxRedirects on line 13 to a very big number or a number u see fit to change it. This worked for me. I never got this error again. It should say maxRedirects: {number}. The default value was set at 3 for me.
(Edited) I just changed it to a big number and it worked perfectly but feel free to change it to any number.
Try this out!

Anastatis on 30 Jun 2020

To implement the above suggestion by @Anastis without changing the miniget code (which will get overridden w/ npm updates), add the following to your ytdl options: requestOptions: { maxRedirects: 10 }. Change maxRedirects to any number you see fit, I haven't tested this much, although I wouldn't suggest making it too big as redirect loops do signal a broken page and will slow down both your client and YouTube. HTTP spec set the standard at 5 (RFC 2616 section 10.3), which Chrome/Firefox and probably others follow, more than miniget's 2 default but still not "a very big number."