My AWS instance stopped and when I restarted it, retool won’t come up again

root@ip-172-16-11-173:/home/ssm-user/retool-onpremise# docker logs 823f7f424512 waiting 15 seconds for postgres:5432 postgres:5432 is available after 0 seconds
not untarring the bundle
[process service types] [ 'MAIN_BACKEND' ]
Failing checking database migrations
(node:22) UnhandledPromiseRejectionWarning: SequelizeConnectionError: password authentication failed for user "retool_internal_user"
at /snapshot/backend/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:182:24
at Connection.connectingErrorHandler (/snapshot/backend/node_modules/pg/lib/client.js:194:14)
at Connection.emit (events.js:315:20)
at Socket. (/snapshot/backend/node_modules/pg/lib/connection.js:134:12)
at Socket.emit (events.js:315:20)
at addChunk (_stream_readable.js:295:12)
at readableAddChunk (_stream_readable.js:271:9)
at Socket.Readable.push (_stream_readable.js:212:10)
at TCP.onStreamRead (internal/stream_base_commons.js:186:23)
(node:22) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without acatch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line API | Node.js v17.7.1 Documentation). (rejection id: 1)
(node:22) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Hi #jhcoinl,

Sorry about the late reply here. Did you by any chance change the POSTGRES_PASSWORD env variable before starting Retool for the first time?

No worries, worked it out with support.. Was the password