n8n + Postgres connection loop / Session error / Application failed to respond
1samuelvesely6
HOBBYOP

17 days ago

Hello,

I’m having a recurring issue with my Railway deployment.

Project:

efficient-blessing

Environment:

production

Problem:

My n8n service keeps failing with:

“Application failed to respond”

At the same time, the Railway Postgres UI keeps looping between:

“Attempting to connect to the database…”

and

“Session error”

with the message:

“We are unable to connect to the database via SSH.”

This already happened yesterday as well.

What I already tried:

  • Restarted both Postgres and n8n

  • Added:

    • DB_POSTGRESDB_CONNECTION_TIMEOUT=60000
    • DB_POSTGRESDB_SSL=true
    • DB_POSTGRESDB_SSL_REJECT_UNAUTHORIZED=false
  • Confirmed that:

    • volumes still exist
    • N8N_ENCRYPTION_KEY still exists
    • services show as Online

Important:

I do NOT want to recreate the deployment because I have existing n8n credentials/workflows connected to Gmail, Bright Data, etc.

It currently looks like:

  • Postgres networking/session issue
  • or Railway SSH/Postgres UI issue

Could you please check the project/networking/database state?

Thanks.

Solved

1 Replies

Railway
BOT

17 days ago

Your n8n service is currently in a crashed state, and this is almost certainly caused by the ongoing major service disruption affecting GCP-hosted workloads, including traffic, networking, and the database UI. Your Postgres service itself shows as healthy (last successful deploy on May 7), so your data and volumes should be intact. Once the incident is fully resolved, redeploy your n8n service and the Postgres connectivity should restore normally - no need to recreate anything.


Status changed to Awaiting User Response Railway 17 days ago


Railway
BOT

10 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 10 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...