You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a very weird and consistent issue happening with the credentials system on both cloud and local docker dev. When you first do a new rollouts or up all the credentials 500 out, seemingly unable to connect to the database.
Error in get_user_integrations: All connection attempts failed
I have to restart my rest server to make it work again. I've reported it earlier as well thought it was a one off, but it's definitely consistently happening now
Steps to replicate:
Start from a fresh install
docker compose build && docker compose up
npm run dev / yarn dev
Go to builder and in network you'll see HTTP 500 errors from the credentials endpoint. In the rest container you will see logs saying: Error in get_user_integrations: All connection attempts failed
Restart rest container, and everything is back to normal
Same thing happens on cloud when upgrading the containers (ie new deploy)
The text was updated successfully, but these errors were encountered:
- Add `/integrations/credentials` endpoint which lists all credentials for the authenticated user
- Amend credential fetching logic in front end to fetch all at once instead of per provider
- Resolves#8770
- Resolves (hopefully) #8613
There's a very weird and consistent issue happening with the credentials system on both cloud and local docker dev. When you first do a new rollouts or up all the credentials 500 out, seemingly unable to connect to the database.
I have to restart my rest server to make it work again. I've reported it earlier as well thought it was a one off, but it's definitely consistently happening now
Steps to replicate:
docker compose build && docker compose up
npm run dev
/yarn dev
Error in get_user_integrations: All connection attempts failed
Same thing happens on cloud when upgrading the containers (ie new deploy)
The text was updated successfully, but these errors were encountered: