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

• 🧵 PostgreSQL Deployment Stuck: Repeated "invalid length of startup packet" errors and Healthcheck failing

• 🧵 Postgres .[proxy.rlwy.net](proxy.rlwy.net) domains not resolving (NXDOMAIN)

• 🧵 Postgres: invalid length of startup packet

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

Your PostgreSQL "invalid length of startup packet" errors mean something (likely health checks or your app) is trying to connect using HTTP instead of the PostgreSQL protocol. Fix it by using the correct connection string format postgresql://postgres:yourpassword@your-db.railway.internal:5432/railway or Railway's DATABASE_URL environment variable, and disable any HTTP health checks on your PostgreSQL service since databases don't need them they're causing these false connection attempts that PostgreSQL rightfully rejects.

i am using prisma, using that i can't connect
```
PGPASSWORD=xxxx psql -h shinkansen.proxy.rlwy.net -U postgres -p xxxx -d railway
```
it can connect via psql

i don't think it's prisma issue since i can connect to a postgresql docker container locally

i wasn't dumb
the solution was adding connect timeout to the uri
for prisma
`?connect_timeout=10`

postgresql://postgres:xxxx@example.net:xxxx/railway?connect_timeout=10

if i accept my own solution will i get the bounty not like i need it

idc

You do not but, I will mark it all the same!