2 months ago
https://primary-production-a4a82.up.railway.app/projects/TAk0uJxVkm1tSk2Z/workflows
My n8n app is not available. I had all processes set up there. Can it be restored?
3 Replies
2 months 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 Railway • 2 months ago
2 months ago
hello, go to your n8n service in railway, go to deployments, hit the 3 dots on the latest deployment and click redeploy. then check the logs to see if it comes back up. your workflows should be safe in a database , and can you share this deploy logs?
2 months ago
Thank you!
Starting Container
Initializing n8n process
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+exporter-trace-ot_496eb58d78a338abeed29b3d8ec5ca2e/node_modules/@n8n/db/src/connection/db-connection.ts:61:13)
at processTicksAndRejections (node:internal/process/task_queues:103:5)
at Start.init (/usr/local/lib/node_modules/n8n/src/commands/base-command.ts:125:3)
at Start.init (/usr/local/lib/node_modules/n8n/src/commands/start.ts:199:3)
at CommandRegistry.execute (/usr/local/lib/node_modules/n8n/src/command-registry.ts:82:4)
at /usr/local/lib/node_modules/n8n/bin/n8n:63:2
Connection terminated due to connection timeout
There was an error initializing DB
Connection terminated unexpectedly
Last session crashed
2 months ago
Okay so your postgres service can't be reached by n8n. go to your railway dashboard and check if your postgres service is running and healthy. if it is, the issue is likely your db env variables on the n8n service. make sure these are set correctly: DB_TYPE, DB_POSTGRESDB_HOST, DB_POSTGRESDB_PORT, DB_POSTGRESDB_USER, DB_POSTGRESDB_PASSWORD, DB_POSTGRESDB_DATABASE. if you're using railway's template variables like ${{Postgres.PGHOST}} make sure they're actually resolving. a quick fix is to switch to the public postgres url (DATABASE_PUBLIC_URL) instead of the private internal host, and also add DB_POSTGRESDB_SSL=true and DB_POSTGRESDB_SSL_REJECT_UNAUTHORIZED=false. then redeploy n8n after saving the vars, i hope this help you