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

bug: YT Music authentication test failed #229

Open
2 tasks done
UditDey opened this issue Nov 14, 2024 · 7 comments · Fixed by #236
Open
2 tasks done

bug: YT Music authentication test failed #229

UditDey opened this issue Nov 14, 2024 · 7 comments · Fixed by #236
Labels
bug Something isn't working fix waiting for release Fix has been committed and waiting for a release to be cut

Comments

@UditDey
Copy link

UditDey commented Nov 14, 2024

Please check existing knowledge before opening an issue

Describe the Bug

I recently started using multi-scrobbler with the pr-203 docker image for YT Music scrobbling. It worked fine for the first week but I just noticed it hasn't been scrobbling tracks for the past 3 days. Opening the dashboard shows this:

[2024-11-14 09:26:17.738 +0000] ERROR  : [App] [Sources] [Ytmusic - MyYTMusic] Authentication test failed!
Error: Authentication test failed!
    at YTMusicSource.testAuth (CWD/src/backend/common/AbstractComponent.ts:235:31)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at YTMusicSource.initialize (CWD/src/backend/common/AbstractComponent.ts:56:13)
    at <anonymous> (CWD/src/backend/index.ts:124:17)
caused by: Error: Credentials exist but API calls are failing. Try re-authenticating?
    at YTMusicSource.doAuthentication (CWD/src/backend/sources/YTMusicSource.ts:155:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at YTMusicSource.testAuth (CWD/src/backend/common/AbstractComponent.ts:229:27)
    at YTMusicSource.initialize (CWD/src/backend/common/AbstractComponent.ts:56:13)
    at <anonymous> (CWD/src/backend/index.ts:124:17)
caused by: Error: Request to https://www.youtube.com/youtubei/v1/account/accounts_list?prettyPrint=false&alt=json failed with status 400
    at HTTPClient.fetch (file://CWD/node_modules/youtubei.js/dist/src/utils/HTTPClient.js:117:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Actions.execute (file://CWD/node_modules/youtubei.js/dist/src/core/Actions.js:66:26)
    at async AccountManager.getInfo (file://CWD/node_modules/youtubei.js/dist/src/core/managers/AccountManager.js:49:26)
    at YTMusicSource.doAuthentication (CWD/src/backend/sources/YTMusicSource.ts:149:17)
    at YTMusicSource.testAuth (CWD/src/backend/common/AbstractComponent.ts:229:27)
    at YTMusicSource.initialize (CWD/src/backend/common/AbstractComponent.ts:56:13)
    at <anonymous> (CWD/src/backend/index.ts:124:17)
[2024-11-14 09:26:17.736 +0000] ERROR  : [App] [Sources] [Ytmusic - MyYTMusic] Additional API response details
    error: {
      "code": 400,
      "message": "Request contains an invalid argument.",
      "status": "INVALID_ARGUMENT"
    }

I've tried reauthenticating and even restarting the whole container but no luck. Upon reauthentication, I enter the code into the google page, the dashboard even says DEBUG : [App] [Sources] [Ytmusic - MyYTMusic] Auth success but the source still remains "idle" and clicking on start results in the output I pasted above

Platform

Docker

Versions

multi-scrobbler:pr-203 Docker image on Ubuntu

Logs

No response

Additional Context

No response

@UditDey UditDey added the bug Something isn't working label Nov 14, 2024
@roos-robert
Copy link

It could very well be related to this: sigma67/ytmusicapi#676 I'm facing the same issue using oauth.

@UditDey
Copy link
Author

UditDey commented Nov 18, 2024

Yes, looks like it. Youtube must have changed the endpoint. oauth itself seems to be working, its just the https://www.youtube.com/youtubei/v1/account/accounts_list?prettyPrint=false&alt=json request that is failing

@tylermiranda
Copy link

yep, can confirm, having the same issue

@FoxxMD
Copy link
Owner

FoxxMD commented Nov 20, 2024

YTM is really throwing wrenches in the gears 🙃 I hope this isn't an effort on their part to block unofficial usage but rather a side effect of regular development evolution but who knows.

I am on semi-vacation at the moment and will have more time to focus on this at the end of the month or December.

@UditDey
Copy link
Author

UditDey commented Nov 21, 2024

I have a hunch this is just a change and not an effort to block us. Also take your time lol, FWIW, I've been using the unofficial YTM desktop app and that has a scrobbling plugin, which is good enough for now.

@FoxxMD
Copy link
Owner

FoxxMD commented Dec 3, 2024

For everyone having auth and history fetching issues: please try out the new authentication methods detailed in #236 using the docker image foxxmd/multi-scrobbler:pr-236

If you try out the new docker image please post any issues you have with it in the issue for #236 instead of this one so I can better keep track of things, thanks.

@FoxxMD FoxxMD linked a pull request Dec 3, 2024 that will close this issue
7 tasks
@FoxxMD
Copy link
Owner

FoxxMD commented Dec 10, 2024

Accidentally closed, but this should be fixed in edge docker image with the merging of #236

@UditDey please try using foxxmd/multi-scrobbler:edge and let me know if its working for you.

You will probably need to get new cookies. After updating your image open Docs on your instance and read the new YT Music configuration section for cookies/oauth to get started. Also check out the FAQ for new YTM troubleshooting directions..

@FoxxMD FoxxMD reopened this Dec 10, 2024
@FoxxMD FoxxMD added the fix waiting for release Fix has been committed and waiting for a release to be cut label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fix waiting for release Fix has been committed and waiting for a release to be cut
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants