Closed gadkarisid closed 3 years ago
I'm seeing the same thing. Looks like there is an API key in lastfm.py that can be changed. I'm going to try it.
I tried my own personal API but the error remains the same
Added a new api key, now in master
If you want to use your own then change this line https://github.com/rembo10/headphones/blob/379fd3d0b83f8dccd3dfbfcd46e33ce479cdc9d0/headphones/cache.py#L22
Thanks @AdeHub! I got the message within the Headphones web UI saying there was an update available, ran the update, and now everything is looking good.
i've tried to change the cache.py file in my docker container, but now it's not even trying to connect to the last.fm api with my key, but with a totally different api key...?
The key i've entered starts with 798 (and is still in the cache.py file after a reboot), the logs say it's giving errors on an api key starting with 395, which is even different from the api key that was in the cache.py file before i made the changes?
When searching for artists, I'm seeing HTTP 403 errors in the logs. Looks like a suspended API key. Here's are the debug messages from the log:
`
`