-
Notifications
You must be signed in to change notification settings - Fork 794
-
Notifications
You must be signed in to change notification settings - Fork 794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error: Status code: 429" Please help me #889
Comments
Fixes courtesy Promise#0001 from the support Discord. |
I am using the latest version but unfortunately it has this problem since yesterday, windows 10 no such problem, only centos broke down in 1 day |
okay uhm, so im using this ytdl-core in my music bot i code in Js, and it works properly for every single commands except the play command, it's always saying 'Error code : 429', idk how to fix it |
There's already an open issue, #635 , that goes into the issue in depth while also providing solutions. |
v4.4.3 works fine but as soon as you upgrade to a newer version, it begins to throw error 429. Weird... |
Should this be closed as a dupe of #635? |
that is strange, the only difference in v4.4.4 was a json fix. no changes to requests or anywhere where it interacted with youtube |
OS : Centos 6 Linux
Node V = v14.16.0
(node:25232) UnhandledPromiseRejectionWarning: Error: Status code: 429
at ClientRequest.httpLib.request (/root/Bots/MrMusic/node_modules/miniget/dist/index.js:190:31)
at Object.onceWrapper (events.js:286:20)
at ClientRequest.emit (events.js:198:13)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:565:21)
at HTTPParser.parserOnHeadersComplete (_http_common.js:111:17)
at TLSSocket.socketOnData (_http_client.js:451:20)
at TLSSocket.emit (events.js:198:13)
at addChunk (_stream_readable.js:288:12)
at readableAddChunk (_stream_readable.js:269:11)
at TLSSocket.Readable.push (_stream_readable.js:224:10)
(node:25232) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:25232) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The text was updated successfully, but these errors were encountered: