Intermittent DB Connection Issues
We are having Intermittent issues connecting to both Postgres and Redis across several environments. Logs appear ok. In some cases the dashboard views is able to show the data in the database, however, in other cases we are seeing the "We are unable to connect to the database over the public network" error."
25 Replies
Project ID:
5d77fb37-1fba-4a55-bbd3-e0fab82437235d77fb37-1fba-4a55-bbd3-e0fab8243723
have you recently done a migration?
Yes
can you connect to the database locally?
yes
can your app connect to the database?
^ logs from our worker talking to Redis
It can connect to Postgres (it could not for several hours) but now it can. It still cannot connect to Redis.
I can connect to the Redis from my local machine. The UI gives the connection string.
okay im seeing a lot of these issues in the help threads, will raise to team
I'm going to reboot our redis using worker.
Still there on reboot
you two know each other?
Yes
We're on a Google Hangout
And work on the same project
same pro team?
Yes
We should be. I started out with a Hobby account. Maybe I'm not linked correctly?
I'm the Pro Team owner in the UI
bug with the discord bot likely
Is there a way to relink?
ive given you the badge manually
This is the URL where I'm grabbing the logs (service removed) https://railway.app/project/5d77fb37-1fba-4a55-bbd3-e0fab8243723/
Hey guys, I am just checking in and trying to find a trend here.
You migrated from V1 to V2, and now you are seeing connectivity issues via the public network?
This is likely related to the #🚨｜incidents we called. The newest updates will always be on our status page.
Could you link to a service that is still showing this?
After a fix we are back. Can you confirm @Ryan! ?
Can confirm, both redis and postgres are back on our end, and our app can connect to both.
for reference these are the DBs that were affected:
Redis: https://railway.app/project/5d77fb37-1fba-4a55-bbd3-e0fab8243723/service/8fe8ed4a-b98e-4f87-b205-0c281ff60f97
Postgres: https://railway.app/project/5d77fb37-1fba-4a55-bbd3-e0fab8243723/service/2f8348dc-02cd-45a1-be3e-d297dc506669
I have a question, and sorry to intrude on this thread.
somehow the deadline to migrate will be extended? as issues are still occurring and still occurring?
We have rolled out a fix and are about to resolve the incident.
The root issue had nothing to do with database migration. We just preferred that you didn't migrate while we were resolving this. New databases seemed to be affected worse and we wanted to limit the exposure to risk. I am not aware of any plans to change the deadline.
gotcha! thanks for the information