MMM-Strava ID Unauthorized

BerkSmash1984

Hello, I am getting client id not authorized, despite having my client ID and client secret correct (from Strava API page). I also have the whitelist setup correctly and can access my MM from my local browser (the MM itself is on a RPI4). I receive the link within the magic mirror and am redirected to the authorization page on Strava, but after clicking authorize and restarting MM, I am still getting the same client ID not authorized. In looking in electron, I do so a ERR_HTTP_HEADERS_SENT error message…

Any help would be greatly appreciated. Screenshots below:

BerkSmash1984

@BerkSmash1984 Opening developer tools shows the following at this point in the authorization:

Note: I have my pihole disabled while testing, as it is also on this RPI

sdetweil

@BerkSmash1984 if your MagicMirror config.js
address:“0.0.0.0”

change to the ip address of the pi

address:“191.168.?.?”

and try again

BerkSmash1984

@sdetweil changed it

No luck though. I see lots of errors with Dev tools from PiHole module if I change from 0.0.0.0 to the IP of the RPI4

mumblebaj

@BerkSmash1984 Did you add your client_id and client_secret to the config,js?

{
                        module: "MMM-Strava",
                        header: "My STRAVA Stats",
                        position: "middle_center",
                        config: {
                                        client_id: "your_client_id",
                                        client_secret: "your_client_secret"
                                        activities: ["ride", "run", "swim"],
                                        period: "all",
                                        stats: ["count", "distance", "achievements"],
                                        units: "metric",
                                        updateInterval: 86400000,
                                        reloadInterval: 86400000

I am using address: “0.0.0.0” and I am not having any issues.

sdetweil

@mumblebaj he posted in discord

BerkSmash1984

@mumblebaj Yes, I did:

BerkSmash1984

@mumblebaj Any ideas here? Would really like to get this functional. Appreciate any help!

mumblebaj

@BerkSmash1984 Let’s trace all the required steps.

Have run npm install in the MMM-Strava folder?
Did you do the browser auth on the PI?
Does the tokens.json file exist in the MMM-Strava folder and does it have the required information in it? This should be created once the authorization step has been completed from the Browser on the RPi and should be populated with some token and user information.

Other than checking that I am not sure what else you can check. Other than starting the process from scratch to re-install and re-auth I don’t know what else you can do.

BerkSmash1984

@mumblebaj Thanks for the response.

yes npm install was run the MMM-Strave folder
yes I did the browser auth on the RPI as well
no, I do not see a tokens file in the MMM-Strava folder after attempting the authorization: