21 days ago
Hi, I'm having trouble logging into my dashboard—it just keeps loading and never completes the login process.
I'm also experiencing issues with my PostgreSQL database connection. I keep getting the following error:
sorry, too many clients already
Could you please help me investigate what might be causing these issues?
Pinned Solution
21 days ago
Too much connections made to your Postgres service, you can deploy PGBouncer to fix this
Open your Postgres service > Open Database Tab > Click on Config > Scroll down a bit and you'll see Connection Pooling section, Click the Add PGBouncer button to deploy PGBouncer infront of your Postgres service
After PGBouncer deploy complete, change DATABASE_URL variable value of your backend service to use ${{PgBouncer.DATABASE_URL}} so that your app will use the bouncer connection
Attachments
7 Replies
21 days ago
We're sorry for the trouble. The dashboard loading issue is caused by an ongoing incident affecting the dashboard and API, and a fix is being rolled out. You can follow updates at this status page. The PostgreSQL "too many clients" error is an application-level connection management issue, separate from the dashboard incident. For help debugging that, we'd recommend posting it as a new thread at station.railway.com/questions where community members can assist.
Status changed to Awaiting User Response Railway • 21 days ago
Railway
We're sorry for the trouble. The dashboard loading issue is caused by an ongoing incident affecting the dashboard and API, and a fix is being rolled out. You can follow updates at [this status page](https://status.railway.com/incident/LJT4X01X). The PostgreSQL "too many clients" error is an application-level connection management issue, separate from the dashboard incident. For help debugging that, we'd recommend posting it as a new thread at [station.railway.com/questions](https://station.railway.com/questions) where community members can assist.
21 days ago
This is coming from the db connection it self on the dashboard
Attachments
Status changed to Awaiting Railway Response Railway • 21 days ago
21 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 21 days ago
21 days ago
Too much connections made to your Postgres service, you can deploy PGBouncer to fix this
Open your Postgres service > Open Database Tab > Click on Config > Scroll down a bit and you'll see Connection Pooling section, Click the Add PGBouncer button to deploy PGBouncer infront of your Postgres service
After PGBouncer deploy complete, change DATABASE_URL variable value of your backend service to use ${{PgBouncer.DATABASE_URL}} so that your app will use the bouncer connection
Attachments
mayori
Too much connections made to your Postgres service, you can deploy PGBouncer to fix this Open your Postgres service > Open Database Tab > Click on `Config` > Scroll down a bit and you'll see Connection Pooling section, Click the `Add PGBouncer` button to deploy PGBouncer infront of your Postgres service After PGBouncer deploy complete, change `DATABASE_URL` variable value of your backend service to use `${{PgBouncer.DATABASE_URL}}` so that your app will use the bouncer connection 
21 days ago
Sadly, i still could not proceed to the config
Attachments
adedamolabasit
 Sadly, i still could not proceed to the config
21 days ago
Maybe you need to temporarily turn off your app that connected to your postgres service
mayori
Maybe you need to temporarily turn off your app that connected to your postgres service
21 days ago
How can i get the the actual url for this ${{PgBouncer.DATABASE_URL}}. my service is actually running on another railway account outside of this
adedamolabasit
How can i get the the actual url for this ${{PgBouncer.DATABASE_URL}}. my service is actually running on another railway account outside of this
21 days ago
You can open the PgBouncer service and copy the variable value of DATABASE_PUBLIC_URL
DATABASE_URL wouldn't work since your backend service environment and project is different from your PgBouncer service
Status changed to Awaiting User Response Railway • 21 days ago
Status changed to Open mayori • 21 days ago
Status changed to Solved mayori • 21 days ago