Read the statement by Michael Teeuw here.
MMM-NowPlayingOnSpotify no longer working?
-
@droidus so are the ports mapped? 8888 on the container to something on the host?
unless u did that, that is not accessible
the request will cause a callback to that system
-
@sdetweil I don’t see port 8888 running on the container.
-
the authorization , step 2
cd authorization node appshould run forever
and app.js uses port 8888
so u have to run this IN the container, right? -
@sdetweil Yes, it looks like the ports are mapped. I can reach the IP/port from my laptop.
-
@droidus ip:8888 right?
so when u open that with your laptop browser, you should see
this page https://github.com/raywo/MMM-NowPlayingOnSpotify/authorization/public/index.html -
@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:
