2 months ago
After upgrading from Personal to Hobby subscription, my private networking between the postgres, n8n, and primary no longer work.
- Project: scintillating-tenderness
- Issue: Private networking broken between Worker and Postgres
- Error: Could not establish database connection within the configured timeout
5 Replies
2 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 Private networking still unreliable for Redis — forced to use TCP proxy for stability
🧵 I'm unable to connect my Rust backend to PostgreSQL using private networking.
If you find the answer from one of these, please let us know by solving the thread!
2 months ago
What kind of app is it? Make sure you are allowing/prefering/forcing IPv6 connections to the database. Had a similar issue and once I moved to IPv6 I never had an issue again.
2 months ago
Looks like n8n doesn’t support the option
bbhoss
What kind of app is it? Make sure you are allowing/prefering/forcing IPv6 connections to the database. Had a similar issue and once I moved to IPv6 I never had an issue again.
2 months ago
N8N worker.
Redis
Postgres.
And primary.
They are all set uo with internal networking and we're working prior to upgrading to the Hobby plan. Now I can only connect my workers to Postgres via public Url, so egress fees are applied.
2 months ago
try this for redis connections, add to both primary and worker:
QUEUE_BULL_REDIS_DUALSTACK=truemake sure all your database connection strings use the private dns names like postgres.railway.internal and redis.railway.internal - not ip addresses.
redeploy after adding the variable
i hope this help you 