FATAL: sorry, too many clients already
Trying to connect to PostgreSQL, getting this error. The database is basically empty and I used it only locally.
If i go to the
data section of the plug-in, railway says Failed to connect to Postgres. Is it accessible to the public?Solution:Jump to solution
turns out it's actually connected and thst is a prisma problem
https://stackoverflow.com/questions/68476229/m1-related-prisma-cant-reach-database-server-at-database5432...
14 Replies
Project ID:
649cb17e-bf89-4494-816a-4dc8cffe9717649cb17e-bf89-4494-816a-4dc8cffe9717
I wonder if it could be that railway failed to connect due to too many clients being connected already
maybe you're connecting to it more than once somewhere else?
Just guessing here
Otherwise you can try increasing the max connections allowed
how are too many clients already connected
I'm using it only locally and didn't even start server
fair
maybe railway is never closing the database connections when you've opened the data tab
I'd recommend removing the variables railway uses to connect to the data tab and restarting the database
We are investigating reports of strange database connection errors (with postgres and mongo) and will add this to our list to check
I'm having issues connecting postgres to nodejs on railway but works locally, can it be because of this?
PrismaClientInitializationError: Can't reach database server at `monorail.proxy.rlwy.net`:`46443That is something different. Is it the same project id?
my money is on the private networking initialisation times issue ðŸ˜
No its
c3046ecc-a875-4e08-a808-2ff3dcd1b7f9Solution
turns out it's actually connected and thst is a prisma problem
https://stackoverflow.com/questions/68476229/m1-related-prisma-cant-reach-database-server-at-database5432
@fedev not a prisma problem, it's a private network initialisation time problem
increasing the connection timeout proves that theory
I see thank you 💯