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

• 🧵 postgres.railway.internal - Private networking

• 🧵 Error: dial tcp: lookup postgres.railway.internal on [xxx.xxx.xxx.xxx](xxx.xxx.xxx.xxx):zz: no such host

• 🧵 Private Domain Networking Timeout — Southeast Asia Region

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

Hello,

You are sharing your database credentials, I hope you are aware of that, if so please reset your db.

also can you verify two things:

1. Ensure that n8n and Postgres are running in the same environment; internal DNS won’t work otherwise.

2. Test the Postgres connection directly using railway run psql.

If the schema is broken there, restore or reset the database. If it isn’t, then it’s likely just a networking mismatch, and disabling SSL internally should resolve it.

Hi, thanks for the guidance.

First, I’ve rotated the Postgres credentials, so the values I shared earlier are no longer valid.

Per your suggestions I’ve checked the following:

1. Same environment

Using the Railway CLI I linked the project:

railway link
# workspace: enrique utiel denia's Projects
# project: Test para DANIA
# environment: production
# service: Postgres

Both services (Primary – n8n and Postgres) are in the same project and in the same environment (production). They appear on the same canvas and share the same environment selector.

2. Testing Postgres connection with railway run psql

From PowerShell on my machine:

railway run psql "$DATABASE_URL"

This uses the internal DATABASE_URL (the one that points to postgres.railway.internal:5432).

The result is:

psql: error: no se pudo traducir el nombre «postgres.railway.internal» a una dirección: Name or service not known

So even inside railway run the hostname postgres.railway.internal cannot be resolved.

For clarity:

• When I configure n8n to use the public proxy URL (DATABASE_PUBLIC_URL) with SSL, everything works fine and n8n can use the database.

• When I configure n8n to use the internal host:

DB_TYPE=postgresdb
DB_POSTGRESDB_HOST=postgres.railway.internal
DB_POSTGRESDB_PORT=5432
DB_POSTGRESDB_DATABASE=railway
DB_POSTGRESDB_USER=postgres
DB_POSTGRESDB_PASSWORD=<************>
DB_POSTGRESDB_CONNECTION_TIMEOUT=60000
# SSL disabled for the internal connection as suggested

n8n cannot connect and times out, and the railway run psql "$DATABASE_URL" command fails with the “Name or service not known” error above.

Given this, it looks like the issue is not with SSL or the schema, but with internal DNS / private networking for postgres.railway.internal in this environment.

Could you please check why postgres.railway.internal is not resolvable from the production environment of the Test para DANIA project, and whether there is any misconfiguration on private networking for this project?

I’m happy to run any additional commands you need and share the output.

Thanks again for your help!

Is there any update on this issue? It seems like I'm facing the exact same issue.

No, I haven't found information on how to solve the problem, but I haven't received any help. The only solution at the moment is to work with public networking.

Thanks for the hint. I was able to set all connections (including workers) to public, so now my workflows execute again. This is really odd, as I haven't changed anything to the configuration.

While debugging, I've also deployed a complete fresh infrastructure project from the template "N8N (w/ workers)" and ran into the same private endpoint connection issues. This seems to be a bigger problem.

Update: This is my current project. First the private connection of the Primary and the Worker instances to Postgres wouldn't work. I fixed this using the public endpoints. Today also the private connection to Redis stopped working. The fix is again using a public connection.

Is there an issue with private connections?

Good morning. It seems that's the case, and I'm not the only one with this problem. Let's see if Railway can tell us what's going on...

Private connection with redis works when you add ?family=0

New to Railway I deployed a PostgreSQL using the Railway template and I had a private network url. I came back to it the next day and in the setting I see "failed to get private networks". It is very worrying that this sudden happens and even more so that I see that this was reported days ago.