Postgres internal networking broken — N8N cannot connect despite healthy DB
atha-nivy
HOBBYOP

3 days ago

Hi Railway team,

My N8N service cannot connect to its Postgres database since July 1st, 05:16 UTC.

Symptoms:

  • Both services show "Online" in dashboard
  • N8N logs: "Database connection timed out" continuously
  • Postgres is healthy: confirmed via console (SELECT 1 works, only 7/100 connections used)
  • Railway Dashboard shows "Connection terminated" when trying to connect via SSH UI

What I tried: Restarted both services — no change.

This looks like a Railway internal private networking issue between the two services.

Project: Clavy N8N and Clavy N8N Staging

Affected services: n8n + Postgres

Please help restore the internal network connection between these two services.

Thank you

$10 Bounty

1 Replies

Railway
BOT

3 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 3 days ago


I assume there aren't any error logs in Postgres?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...