Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 from cloud login #241

Closed
ikke-t opened this issue Jul 23, 2022 · 2 comments
Closed

404 from cloud login #241

ikke-t opened this issue Jul 23, 2022 · 2 comments

Comments

@ikke-t
Copy link

ikke-t commented Jul 23, 2022

Hi,

I tried setting up plejd on raspi3, and got stuck at this after configuring and restarting plejd:

2022-07-23 10:12:23 DBG [plejd-api] sending POST to https://cloud.plejd.com/parse/login
2022-07-23 10:12:24 ERR [plejd-api] Unable to retrieve session token response:  Request failed with status code 404
Error: Request failed with status code 404
    at createError (/plejd/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/plejd/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/plejd/node_modules/axios/lib/adapters/http.js:269:11)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
2022-07-23 10:12:24 ERR [plejd-api] Api request failed, no cached fallback available Converting circular structure to JSON

I have checked my credentials from gui and yaml, they are fine. This is what configs looks like:

site: Mökki
username: foo@bar.com
password: hidd3n*&secret
mqttBroker: mqtt://localhost
mqttUsername: secret-user
mqttPassword: secret
includeRoomsAsLights: false
preferCachedApiResponse: false
updatePlejdClock: true
logLevel: debug
connectionTimeout: 2
writeQueueWaitTime: 400

Any ideas? The internet from raspi should work fine, as ha succesfully updated several components, and installed and built plejd. Also time seems to be ok.

@ikke-t
Copy link
Author

ikke-t commented Jul 23, 2022

Looking at the code, could the appid have changed? If creds were wrong, it would return 403 I assume.

@ikke-t
Copy link
Author

ikke-t commented Jul 23, 2022

Sorry for the noise. I had likely something wrong with pwd. I reset my pwd and it works now. I wonder why the return code could was 404?

@ikke-t ikke-t closed this as completed Jul 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant