[i] An error occurred while processing the query

[LiterallyNoOne1]

Hello! I've been using freyr for a while, but after using it most recently, it stopped working.

It just ends up doing this. Funnily enough, I did this on a fresh install of Windows since my SSD recently just died out of nowhere, and yet it's the same error that I was getting before. I installed through the manual method. Tried Docker before on my old install of windows, but ran into issues, so I just ended up installing it manually... I don't think I did anything wrong as I followed the install instructions in order, so not sure what's happening or if this is a new bug, cause I had checked the previous issues and there was nothing about this..

    ____
   / __/_______  __  _______
  / /_/ ___/ _ \/ / / / ___/
 / __/ /  /  __/ /_/ / /
/_/ /_/   \___/\__, /_/
              /____/ v0.9.0

freyr - (c) Miraculous Owonubi <[email protected]>
------------------------------------------------------
Checking directory permissions...[done]
[https://open.spotify.com/album/0m6kc29nRTIRiJirbsSuCC?si=7e26921c9bfa46b3]
 [•] Identifying service...[Spotify]
 [•] Checking authentication...[unauthenticated]
 [Spotify Login]
  [•] Logging in...[done]
 Detected [album]
 Obtaining album metadata...(failed: [[object Object]])
 [i] An error occurred while processing the query
============ Stats ============
 [•] Runtime: [621ms]
 [•] Total queries: [01]
 [•] Total tracks: [00]
     » Skipped: [00]
     ✓ Passed:  [00]
     ✕ Failed:  [00]
 [•] Output directory: [.]
 [•] Total Output size: 0.00 B
 [•] Total Network Usage: 0.00 B
     ♫ Media: 0.00 B
     ➤ Album Art: 0.00 B
 [•] Output bitrate: 320k
===============================

[scottfridwin]

From what I can see, this issue is actually a 429 (Too many requests) error code being returned from the Spotify API. I'm assuming that the clientId/clientSecret built into the image are either being used by too many people or have been revoked.

Not totally sure, but I think you should be able to fix it by:

• Removing the spotify tokens in the user-specific configuration file (d3fault.x4p). These were generated with the built-in clientId/clientSecret, so I don't think they will work again.
• Replace the clientId/clientSecret in the project configuration file (conf.json) with your own id and secret.
• Remove the refresh token from conf.json as well.

It'd be nice to have a cli option that can remove current authentication values, so maybe I'll try to put that in a PR.

[LiterallyNoOne1]

I think I tried that after reading your fix but unless I did that wrong, it's still returning the same error

[scottfridwin]

I was able to make it work with new clientId/clientSecret values. There's another error that pops up related to the version of yt-dlp that is being used (see here), but I think the only way to solve that is to rebuild freyr-js.

Just to clarify, this is what should fix it:

1. Follow these instructions to get my own clientId and clientSecret value.
2. Remove the services:spotify:expiry, services:spotify:access_token, and services:spotify:refresh_token from my d3fault.x4p file.
3. Remove the services:spotify:refreshToken value from my conf.json file.
4. Replace services:spotify:clientId and services:spotify:clientSecret values in conf.json with the new values.
5. Run freyr.

It should pop open a browser to http://localhost:36346 asking for spotify authentication, which will use the new values to generate a working access token. If you're using the docker container I'm not sure how to make the web authentication bit work. But if the web authentication never happens, it isn't using the new clientId/clientSecret.

[LiterallyNoOne1]

So now it gets much further than before - But then it hits me with these

[LiterallyNoOne1]

I had followed your instructions 1-to-1 to get this far, so that definitely helped out, but now this is a different error - I didn't do this through docker so I don't actually have the ability to do the same fix suggested in similar issues, unless there was already a fix for manual installations...

[scottfridwin]

Does that have the same "Unable to extract uploader id" error as #450? It would be up earlier in the output than what you posted.

If it is that issue, try running this:
python3 -m pip install yt-dlp==2023.02.17.334
source: https://levelup.gitconnected.com/fix-error-unable-to-extract-uploader-id-3fad389322a7

[LiterallyNoOne1]

No, it does not have the "Unable to extract uploader id", i actually looked into that before posting - If anything, this error actually goes entirely past that point that it's been hitting. #442 actually has the same error, but I'm unsure how to fix it without using Docker.

[scottfridwin]

Hmm, looks like the fix for #442 was to update yt-dlp as well. Are you able to rebuild freyr from source? That should be similar to what I did with a new local docker image.

Beyond that I'm not sure I can be of any more help. Maybe someone else will be able to chime in and get it working.

[miraclx]

Hey guys, found some time to look into these..

Obtaining album metadata...(failed: [[object Object]])

Not a very helpful error, patched that in a dep.. thelinmichael/spotify-web-api-node#484

That said, I've had to recreate new credentials for freyr - #454. I'll drop a full release soon.