22 days ago
Our Postgres service's own Database tab fails to connect with 'no PostgreSQL user name specified in startup packet,' and PGUSER/PGPASSWORD show empty on the production environment, but the app itself is still running on an existing connection.
Pinned Solution
22 days ago
you do have the credentials - your app is still connecting, so they're in its DATABASE_URL. go to your app service → Variables, reveal DATABASE_URL, it looks like postgresql://USER:PASSWORD@host:5432/railway. the user is usually postgres.
copy that user and password into PGUSER and PGPASSWORD on the postgres service (check POSTGRES_USER / POSTGRES_PASSWORD there too if they're also blank), then redeploy the postgres service. the database tab uses those vars to connect, that's why it says "no user name in startup packet" while your app keeps working.
dont touch the app's DATABASE_URL while doing this and your data is safe, its on the volume.
4 Replies
22 days ago
The Postgres service logs confirm repeated "no PostgreSQL user name specified in startup packet" errors, which means connection attempts are arriving without credentials. Our tools can see that PGUSER and PGPASSWORD variables are defined on the service but cannot confirm their values. If they are genuinely blank in your dashboard's Variables tab, you can re-set them to valid credentials (the username and password your Postgres instance was provisioned with) and redeploy, which will also fix the Database tab connection.
Status changed to Awaiting User Response Railway • 22 days ago
Railway
The Postgres service logs confirm repeated "no PostgreSQL user name specified in startup packet" errors, which means connection attempts are arriving without credentials. Our tools can see that PGUSER and PGPASSWORD variables are defined on the service but cannot confirm their values. If they are genuinely blank in your dashboard's Variables tab, you can re-set them to valid credentials (the username and password your Postgres instance was provisioned with) and redeploy, which will also fix the Database tab connection.
22 days ago
I don't have the username and password your Postgres instance was provisioned with
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 22 days ago
22 days ago
Hey, try re-generating credentials on the Database tab
Attachments
ianm2401
I don't have the username and password your Postgres instance was provisioned with
22 days ago
you do have the credentials - your app is still connecting, so they're in its DATABASE_URL. go to your app service → Variables, reveal DATABASE_URL, it looks like postgresql://USER:PASSWORD@host:5432/railway. the user is usually postgres.
copy that user and password into PGUSER and PGPASSWORD on the postgres service (check POSTGRES_USER / POSTGRES_PASSWORD there too if they're also blank), then redeploy the postgres service. the database tab uses those vars to connect, that's why it says "no user name in startup packet" while your app keeps working.
dont touch the app's DATABASE_URL while doing this and your data is safe, its on the volume.
Status changed to Solved brody • 21 days ago