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 changed the CLIENT_ID to a client-id I own from soundcloud API and it works again. I guess the client-id hardcoded is expired/revoked/ban.
Feature request
It would be cool to add a --client-id argument to override hardcoded client-id. You can create your own API Client ID via https://soundcloud.com/you/apps and then use this client-id. This could provide an easy-way to bypass 401 when hardcoded client-id is not working anymore.
In addition, it could helps to debug/confirm issue related to client-id without modifying the code. This could not be limited to soundcloud.
The text was updated successfully, but these errors were encountered:
@dstftw Hello, I think referring this issue on the commit and not closing it would have been better. This issue is mainly about the feature request, not only about the issue.
Prerequisites
What is the purpose of your issue?
Issue
Soundcloud extractor returns HTTP 401, after search on existing issues, it looks like CLIENT_ID on the code needs to be updated.
Related Issues: #11327 and #12376
I changed the CLIENT_ID to a client-id I own from soundcloud API and it works again. I guess the client-id hardcoded is expired/revoked/ban.
Feature request
It would be cool to add a
--client-id
argument to override hardcoded client-id. You can create your own API Client ID via https://soundcloud.com/you/apps and then use this client-id. This could provide an easy-way to bypass 401 when hardcoded client-id is not working anymore.In addition, it could helps to debug/confirm issue related to client-id without modifying the code. This could not be limited to soundcloud.
The text was updated successfully, but these errors were encountered: