Hey there! We've found the following might help you get unblocked faster:

• 🧵 n8n redis timed out after update

• 🧵 n8n redis connection timing out after update

• 🧵 ❗Service stops scraping after a while - no crash, no logs - Hobby Plan

If you find the answer from one of these, please let us know by solving the thread!

I am also facing the same issue. The n8n instances cant seem to connect to the postgres instance

Did you try "Deploy latest commit" on both the primary and worker services? Are there any errors in the output of either services that could provide more background of the issue?

Hey! Most likely the crash happened because the Node version or environment variables changed after redeploy

Set Node.js to the version supported by your n8n version

Recheck all environment variables DB URL API keys

Redeploy

This usually fixes the service crash

Hey, I'm running into the same error. I was facing a postgres volume limit and increased the volume. After that, I tried to redeploy the Primary instance, but it keeps crashing, as it cannot establish a connection to the Postgres instance. I checked all the environment variables, but they all seem fine in both Postgres and Primary instance. I can also connect to the Postgres locally. There seems to be a network issue, which I cannot pin down. This is the output of the Primary logs:

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._4f71e79debd90f68b8a49d1bf4d1af69/node_modules/@n8n/db/src/connection/db-connection.ts:57: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:202:3)

at CommandRegistry.execute (/usr/local/lib/node_modules/n8n/src/command-registry.ts:66:4)

at /usr/local/lib/node_modules/n8n/bin/n8n:63:2

Connection terminated due to connection timeout

Last session crashed

What I've done:

• check environment variables

• increase DB_POSTGRESDB_CONNECTION_TIMEOUT to 60000

• Create a complete new project and install the template (-> runs into same issue)

Any help is appreciated!

Did you find a solution?

Resolve Mobile UI Overlapping Bug

Description:
Some UI components overlap on screens below 360px width. Need layout fixes, responsive breakpoints, and testing on multiple devices.

Description:
Some UI components overlap on screens below 360px width. Need layout fixes, responsive breakpoints, and testing on multiple devices.

same issue.
But I tried to deploy from different railway account, using this same template, and after crashing first time, it deployed with the second try.
No luck on this account however.

I think there's a general issue with Railway and the internal networking. I'm not using N8n but I'm having the exact same issue. Internal networking seems to not work at all in my new project. Using public Host & Port / URL works everytime. So far i've tried with a Mysql DB, Redis and MinIO service..

Did that resolution work? Have you had any additional luck or same problem?