-
-
Notifications
You must be signed in to change notification settings - Fork 403
Newbie: On launch webui shows 3 errors: 'Failed to load/fetch...' #710
-
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 4 comments · 12 replies
-
Can you share the contents of |
Beta Was this translation helpful? Give feedback.
All reactions
-
Sure:
} webui.local.json:
} |
Beta Was this translation helpful? Give feedback.
All reactions
-
I've since created a configuration.local.json in the p2g-webui directory as well, but that doesn't seem to change any behaviour. I wonder if I created the directory structure wrong? Does this look right? . |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
That looks correct, other than the |
Beta Was this translation helpful? Give feedback.
All reactions
-
Oh, I think I know what I did wrong... and on top of that I also got the the documentation for this change wrong 😞 @kcorey, try renaming |
Beta Was this translation helpful? Give feedback.
All reactions
-
That did change the behaviour! I have access to the /settings now. So, I was able to enter my Peloton and Garmin credentials. I was able to sign onto Peloton via the website with this credential. To be sure, I reset it, and was able to login on the web with this new password. However, when I load the app, it originally failed as unauthorised, and then later with 'Too many retries'. Do I need to create a separate account or an API access for my Peloton account? -Ken Here's the log file, if that helps.2025-01-04 13:33:41.261 -06:00 [INF] Retry Policy - "https://api.onepeloton.com/auth/login" - attempt 1
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Then again... I went to the console, and recorded the network activity when I logged in using my (working) credentials. At no point did it make a GET or a POST to https://api.onepeloton.com/auth/login...so I can't follow that pattern. Is the API still supported? In the UK? |
Beta Was this translation helpful? Give feedback.
All reactions
-
This looks like normal behavior when P2G spams the Peloton API with too many failed auth requests.
Nope, shouldn't need anything special. I would try the following:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
As an update, I started it this morning to try to erase the cxredentials, and it worked fine. Peloton simply had to cool down, I guess. |
Beta Was this translation helpful? Give feedback.
All reactions
-
same problem after update P2G V 4.4.0 Linux debian |
Beta Was this translation helpful? Give feedback.
All reactions
-
I think I know why @kcorey is seeing the error, but I'm less certain why you are @k0ns013 since it sounds like all you did was upgrade an existing install, which should just work. Do you mind showing me your |
Beta Was this translation helpful? Give feedback.
All reactions
-
update from peloton-to-garmin-4.3.1 to version peloton-to-garmin-4.4.0, no problems with version 4.3.1. Version 4.4.0 has the error described above.
p2g-webui log:
p2g-api
I hope this helps you |
Beta Was this translation helpful? Give feedback.
All reactions
-
It looks like you probably updated your If you'd like to keep it on the updated version using the new environment variable, then you'll need to make changes similar to this and ensure you have changed the directory structure to match the new volume mappings. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
problem solved with tip , THX |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
Oh, I think I know what I did wrong... and on top of that I also got the the documentation for this change wrong 😞
@kcorey, try renaming
api.local.json
andwebui.local.json
so that they are both namedconfiguration.local.json
and give it another go? (you'll still have two separate files, but they both need to be namedconfiguration.local.json
)