Open Nowaha opened 5 months ago
any updates?
It's still happening, but perhaps it's a persistent SSL issue on Spotify's end (so maybe we HAVE to set CURLOPT_SSL_VERIFYPEER
, which is also done in another request already)
@akashrchandran will have to set a custom user-agent to his calls to Spotify servers. Spotify has started blocking the internal API calls with custom user-agents. I have implemented a similar thing at https://github.com/aviwad/LyricFever/commit/682b60f0b1907d728c3975a015a6b165b2785ced as has https://github.com/raitonoberu/lyricsapi/commit/659da1d2b9064997562ddec8586f2aefd9254d42
Nevermind Spotify has started blocking free accounts once again. Damnit.
Are you using an ad blocker or have you blacklisted spclient.wg.spotify.com in your hosts file, or something similar?
@akashrchandran I do not and have not, no
It doesn't matter whether I use
?trackid=
or?url=
, but with any track (even the ones given as an example in the readme), I always get:{ "error": true, "message": "lyrics for this track is not available on spotify!" }
as a response, despite me having the lyrics on my other monitor.
Not sure if I did something wrong setup wise, I did retrieve my
SP_DC
minutes prior.When running the CURL request verbose, I see this:
Setting
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);
seems to be a fix, but I don't know if we should be doing this.