NocoDB Update Failure: Deployment Failed During Network Process (Health Check)

candide

PROOP

2 years ago

Hi! I'm self-hosting nocodb with Railway, and tried to re-deploy to upgrade from 0.255.2 to 0.257.0, and ran into a health check error.

Project ID: 4f84fe2f-87f4-4629-b73b-0ffc633c0d44

Closed

5 Replies

candide

PROOP

2 years ago

Build Logs:

Attempt #1 failed with service unavailable. Continuing to retry for 4m59s
Attempt #2 failed with service unavailable. Continuing to retry for 4m58s
Attempt #3 failed with service unavailable. Continuing to retry for 4m56s
Attempt #4 failed with service unavailable. Continuing to retry for 4m52s
Attempt #5 failed with service unavailable. Continuing to retry for 4m43s
Attempt #6 failed with service unavailable. Continuing to retry for 4m27s
Attempt #7 failed with service unavailable. Continuing to retry for 3m57s
Attempt #8 failed with service unavailable. Continuing to retry for 3m27s
Attempt #9 failed with service unavailable. Continuing to retry for 2m57s
Attempt #10 failed with service unavailable. Continuing to retry for 2m27s
Attempt #11 failed with service unavailable. Continuing to retry for 1m57s
Attempt #12 failed with service unavailable. Continuing to retry for 1m27s
Attempt #13 failed with service unavailable. Continuing to retry for 57s
Attempt #14 failed with service unavailable. Continuing to retry for 27s
 
1/1 replicas never became healthy!
Healthcheck failed!

candide

PROOP

2 years ago

Deploy Logs:

Failed to decrypt any source or integration. Please configure correct encryption key.
Error: Failed to decrypt any source or integration. Please configure correct encryption key.
at t.default [as handler] (/usr/src/app/docker/main.js:2:2333236)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NcUpgrader.upgrade (/usr/src/app/docker/main.js:2:2307440)
at async InstanceWrapper.useFactory [as metatype] (/usr/src/app/docker/main.js:2:1885383)
at async Injector.instantiateClass (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:369:37)
at async callback (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:65:34)
at async Injector.resolveConstructorParams (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:144:24)
at async Injector.loadInstance (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:70:13)
at async Injector.loadProvider (/usr/src/app/node_modules/@nestjs/core/injector/injector.js:97:9)
at async /usr/src/app/node_modules/@nestjs/core/injector/instance-loader.js:56:13

brody

EMPLOYEE

2 years ago

the health check failing is the absolute least of your worries, it has failed because the app never started up.

unfortunately we aren't able to provide support for 3rd party software, so i would recommend asking in the nocodb community about that error in your deploy logs.

candide

PROOP

2 years ago

I reached out to the NocoDB devs, and they helped me solve it:

I just had to copy the nc_auth_jwt_secret value in the nc_store table of the Postgres database, paste it in the deployment's NC_AUTH_JWT_SECRET value, then redeploy.

brody

EMPLOYEE

2 years ago

awsome!

Welcome!