Read the statement by Michael Teeuw here.
MMM-NowPlayingOnSpotify no longer working?
-
@sdetweil Correct. I see that.
-
@droidus and u fill in the fields from the spotify dev account
what did you do for this step in the doc?u had to do the host address, right?
Click on “Edit Settings” and add http://localhost:8888/callback to the Redirect URIs and save your settings.
I just did this on my spotify account and it brought up the auth page as expected… and authorize click brought the page with the code in
-
@sdetweil so before for the ip, I was using my 192. address, but I tried localhost, and it errors saying: “INVALID_CLIENT: Invalid redirect URI”.
-
@droidus I did that, forgot to add the /callback on the redirect on the Spotify page and the mapped port is 8888 on both sides, yes?
on the host opens the auth page from the container
-
@sdetweil This is what I am seeing after entering those fields:
-
@droidus so , is there any info on the node app running in the container?
also open the developers window on the auth page before login, ctrl-shift-i on the keyboard, select the console tab
-
@sdetweil Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.spotify.com/v1/me. (Reason: CORS request did not succeed). Status code: (null).
-
https://github.com/raywo built some nice modules but they are now unmaintained since 4 years. So there will be no fixes, may you find a fork which is still maintained.
You could may fix it using a cors proxy (google will help) or you could use the built in cors proxy of mm which is not released yet (you have to use the
developbranch for this).You find the url to proxy in this line.
-
@droidus try changing the redirect uri on spotify back to using localhost
