3 days ago
Connection terminated due to connection timeout
Last session crashed
Initializing n8n process
There was an error initializing DB
Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DB_POSTGRESDB_CONNECTION_TIMEOUT' environment variable.
Error: Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DB_POSTGRESDB_CONNECTION_TIMEOUT' environment variable.
at DbConnection.init (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+db@file+packages+@n8n+db_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1._cd36ea6afcefbcc83017981a3488f5e9/node_modules/@n8n/db/src/connection/db-connection.ts:55:13)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Start.init (/usr/local/lib/node_modules/n8n/src/commands/base-command.ts3)
at Start.init (/usr/local/lib/node_modules/n8n/src/commands/start.ts:201:3)
at CommandRegistry.execute (/usr/local/lib/node_modules/n8n/src/command-registry.ts:64:4)
at /usr/local/lib/node_modules/n8n/bin/n8n:63:2
Connection terminated due to connection timeout
Last session crashed
Initializing n8n process
There was an error initializing DB
Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DB_POSTGRESDB_CONNECTION_TIMEOUT' environment variable.
Error: Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DB_POSTGRESDB_CONNECTION_TIMEOUT' environment variable.
at DbConnection.init (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+db@file+packages+@n8n+db_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1._cd36ea6afcefbcc83017981a3488f5e9/node_modules/@n8n/db/src/connection/db-connection.ts:55:13)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Start.init (/usr/local/lib/node_modules/n8n/src/commands/base-command.ts3)
at Start.init (/usr/local/lib/node_modules/n8n/src/commands/start.ts:201:3)
at CommandRegistry.execute (/usr/local/lib/node_modules/n8n/src/command-registry.ts:64:4)
at /usr/local/lib/node_modules/n8n/bin/n8n:63:2
Connection terminated due to connection timeout
Last session crashed
Initializing n8n process
There was an error initializing DB
Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DB_POSTGRESDB_CONNECTION_TIMEOUT' environment variable.
Error: Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DB_POSTGRESDB_CONNECTION_TIMEOUT' environment variable.
at DbConnection.init (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+db@file+packages+@n8n+db_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1._cd36ea6afcefbcc83017981a3488f5e9/node_modules/@n8n/db/src/connection/db-connection.ts:55:13)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Start.init (/usr/local/lib/node_modules/n8n/src/commands/base-command.ts3)
at Start.init (/usr/local/lib/node_modules/n8n/src/commands/start.ts:201:3)
at CommandRegistry.execute (/usr/local/lib/node_modules/n8n/src/command-registry.ts:64:4)
at /usr/local/lib/node_modules/n8n/bin/n8n:63:2
Connection terminated due to connection timeout
Last session crashed
4 Replies
3 days ago
Hey there! We've found the following might help you get unblocked faster:
🧵 n8n primary deployments fails after removing cron schedule
🧵 Railway Support Request - Internal Database Connection Failure
If you find the answer from one of these, please let us know by solving the thread!
3 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 3 days ago
3 days ago
Did you change anything before this happened?
Also check that your database volume has space.
phoenixauro
Did you change anything before this happened?Also check that your database volume has space.
3 days ago
No changes. Cant update since first relese... have space and everything else..
160 MB / 5GB
3 days ago
Have you set the variables in your service properly
Attachments