Restarting - Waiting for a platform to initialize
-
Hello,
This is what I got:
curl https://my.flaxxa.in/openid/.well-known/openid-configuration
{"authorization_endpoint":"https://my.flaxxa.in/openid/auth","claims_parameter_supported":false,"claims_supported":["sub","email","email_verified","family_name","given_name","locale","name","preferred_username","picture","groups","sid","auth_time","iss"],"code_challenge_methods_supported":["S256"],"grant_types_supported":["authorization_code","implicit","refresh_token"],"issuer":"https://my.flaxxa.in/openid","jwks_uri":"https://my.flaxxa.in/openid/jwks","authorization_response_iss_parameter_supported":true,"response_modes_supported":["form_post","fragment","query"],"response_types_supported":["code","id_token","id_token token","code id_token","code token","code id_token token","none"],"scopes_supported":["openid","offline_access","email","profile","groups"],"subject_types_supported":["public"],"token_endpoint_auth_methods_supported":["client_secret_basic","client_secret_jwt","client_secret_post","private_key_jwt","none"],"token_endpoint_auth_signing_alg_values_supported":["HS256","RS256","PS256","ES256","EdDSA"],"token_endpoint":"https://my.flaxxa.in/openid/token","id_token_signing_alg_values_supported":["RS256"],"pushed_authorization_request_endpoint":"https://my.flaxxa.in/openid/request","request_parameter_supported":false,"request_uri_parameter_supported":false,"userinfo_endpoint":"https://my.flaxxa.in/openid/me","claim_types_supported":["normal"]}@flaxxain can you put the app in recovery mode, then open a Web terminal and run that curl again?
-
No, I did that way before but it's not working at all.
When I clicked on the 'x' icon it got me this error in console:I hope this helps.
-
No, I did that way before but it's not working at all.
When I clicked on the 'x' icon it got me this error in console:I hope this helps.
@flaxxain thanks for the screenshot! the issue is not with the app, the platform is not starting for some reason. Can you check
/home/yellowtent/platformdata/logs/box.log? You can dosystemctl restart boxand then the logs will tell you why some addon/service is not starting. -
I tried to restart using the command and then I checked the logs:
I got the error:
2025-01-09T18:09:30.199Z box:services Attempt 1 failed. Will retry: Network error waiting for postgresql: Timeout of 20000ms exceeded
-
These are logs, nothing to see.. no errors when I ran the command you sent now.
These are my services currently:
https://prnt.sc/zWs6KktVUYn-What's going on with the system? I'm not at all sure.
-
Ok, I did that, cleaned the postgres and then restart the container as well, but still nothing works.
What should I do?
-
@flaxxain not sure why/how, but docker was corrupt. The box code was unable to reach the containers (like postgresql) via http . Solution was to run
cloudron-support --recreate-dockerwhich re-creates docker from scratch (without destroying any data). -
J joseph has marked this topic as solved on
-
J joseph forked this topic on
-
J joseph locked this topic on