lyarenei
commented
2 years ago Hi, are you sure you are using Listenbrainz API key? I'm not that much familiar with Picard (I use it only for some basic tagging, I usually use beets for handling my music), but I can't think of any reason why Picard should have some integration with Listenbrainz. If you are using some other API key, then you need to use the Listenbrainz API key for this plugin (looks like they call it user token now).
Other than that, I have no idea. All I can think of is some trailing whitespace characters, but it seems that the server handles them without any issues. I tested mine key just now with 20220108.15-unstable-ls781 and my API key validates successfully. You can try the newst JF build if you haven't already - there could be something weird happening, though I don't really believe it.
Also, if the Listenbrainz API returns that the key is invalid, but the key is correct (in the logs), it might be an issue on the Listenbrainz side. Did you try to regenerate and use another API key?
You can also enable debug logging in JF to get more detailed info. After enabling it, you should see the validation request URL and raw response.
That said, sorry for not noticing the issue sooner, it seems that I can't properly set up the notifications or something.. 🤦
Hi, I'm having this error on:
using lastest plugin v2.0.0.0 from 10.8.x repo TrueNAS Scale 22.02-RC.2 Linuxserver.io version:- 20211211.10-unstable-ls764 Build-date:- 2021-12-26T19:19:32+01:00
Always gives me the same error, the key works it's being used on MB Picard without errors.
Can you help me workout why, its failing?