Unable to connect to Postgres from server service
infomiho
PROOP

2 months ago

Deploying a Wasp app which deploys a Node.js server that uses Prisma to connect to the PostgreSQL database.

It fails with:

Error: P1001: Can't reach database server at `postgres.railway.internal:5432`

Link to error: https://railway.com/project/8ec80fa2-dadd-4c4b-879f-e4deb286fb95/service/ffeb3b8f-6edd-43ab-b847-cf706f297de3?environmentId=bb3c85a0-781a-4f69-bf41-47c1b1d3a04e&id=d4dbf971-1669-4c01-bc58-87abfe4f986e&permalink=2025-10-13T10%3A51%3A34.260599658Z&start=1760352630698&end=1760352694260

I'm using ${{Postgres.DATABASE_URL}} as the DATABASE_URL so nothing wild going on. This setup has worked 20-30 times without fault so far.

4 Replies

brody
EMPLOYEE

2 months ago

Hello,

This is because your info @ wasp email Railway account has priority boarding enabled, this has enabled the beta IPv4 private network on your Wasp workspace.

The IPv4 private networking has an issue where some packets get dropped, this is known and being worked on.

For now, please disable that feature flag, and completely recreate the environment.

Railway
BOT

2 months ago

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

infomiho
PROOP

2 months ago

Sweet, good to know it's being worked on, thanks Brody! 👍

brody
EMPLOYEE

2 months ago

No problem!

Railway
BOT

2 months ago

✅ The ticket Packet Loss in Private Networking has been marked as completed.

Railway
BOT

2 months ago

✅ The ticket Packet loss in Private Networking has been marked as completed.

brody
EMPLOYEE

2 months ago

Hello,

Update here: The previously mentioned issues with IPv4 private networking have been fixed. However, you will need to redeploy the affected services.

Loading...