Skip to content
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

Unhandled Promise Error 403 #57

Open
rvishwajith opened this issue Jul 4, 2020 · 4 comments
Open

Unhandled Promise Error 403 #57

rvishwajith opened this issue Jul 4, 2020 · 4 comments

Comments

@rvishwajith
Copy link

rvishwajith commented Jul 4, 2020

I got this error

 % crunchyroll-dl -i https://www.crunchyroll.com/demon-slayer-kimetsu-no-yaiba/episode-19-hinokami-786932 -u [REDACTED] -p [REDACTED] -s soft --language enUS
i crunchyroll-dl v2.0.1
i Attempting to login...
i Successfully logged in!
i Attempting to fetch episode...
(node:2852) UnhandledPromiseRejectionWarning: Error: Request failed with status code 403
    at createError (/usr/local/lib/node_modules/crunchyroll-dl/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/usr/local/lib/node_modules/crunchyroll-dl/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/crunchyroll-dl/node_modules/axios/lib/adapters/http.js:236:11)
    at IncomingMessage.emit (events.js:214:15)
    at endReadableNT (_stream_readable.js:1178:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
(node:2852) 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: 2)
(node:2852) [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

Not sure what the solution is, the other 403 issue was unrelated from what I can tell.

@Noctunus
Copy link

Noctunus commented Jul 5, 2020

Sorry I got no solution for you but only a hint: You should really mask your username/password.

@rvishwajith
Copy link
Author

Oops my bad. Fixed it.

@Gurkward
Copy link

Gurkward commented Jul 5, 2020

Yea sorry same as Noctunus, got no solotuion but we can still access the unedited version of the issue, so make sure to change it asap if you haven't already, on all services you've used it on ofc.

@rvishwajith
Copy link
Author

Thanks it should be gone for good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants