3 months ago
I’m currently using PostgreSQL with the image
ghcr.io/railwayapp-templates/postgres-ssl:17 on the Hobby Plan.
Occasionally, my application fails to connect to the database and returns an error like “can’t access database / connection busy.” This usually happens under normal traffic, not during deployments.
Could you please help me with:
Whether this issue is related to connection limits on the Hobby Plan?
If upgrading my plan would increase the connection limit or improve stability?
Any recommended best practices (connection pooling, settings, etc.) for this setup?
Thank you for your help.
6 Replies
3 months ago
I don't think it is a plan issue, how are you connecting to said DB? What client?
3 months ago
This is of no real help but I am having similar issues following their maintenance today. The connection thread seems to keep getting killed the moment it starts, then it restarts and we end up in a loop. I hope they fix it soon.
I seem to be running into this issue as well, did you ever figure it out? I have an old deployment/commit that seems to work 100% of the time as long as i remove the latest deployment and redeploy it. but trying to move forward a commit to a deployment that just adds some functionality that doesn't get executed unless it's requested by the user it usually fails to deploy completely. Sometimes it does manage to deploy then the requests start failing due to not being able to connect to the host. I ssh in and it seems to work fine with psql from the shell. This really doesn't make sense and is frustrating. Of course no issues with it on my machine 😅
pushed another new commit and now it's seemingly fixed…but I did change some vars including allows ipv6 db connection