monorail.proxy.rlwy.net:
26206
a year ago
The connection to monorail.proxy.rlwy.net`:`26206` suddenly stopped working. My app used to work and I could access my database through `postgresql://<username>:<password>@monorail.proxy.rlwy.net:26206/<database>`. On Aug 20, 2024, at around 9:27 AM MST, my server connections started to fail.
Logs excerpt:
Please make sure your database server is running at `monorail.proxy.rlwy.net`:`26206`.
Invalid `prisma.event.findFirst()` invocation: Can't reach database server at `monorail.proxy.rlwy.net`:`26206` Please make sure your database server is running at `monorail.proxy.rlwy.net`:`26206`.
Can't reach database server at `monorail.proxy.rlwy.net`:`26206`
Please make sure your database server is running at `monorail.proxy.rlwy.net`:`26206`.I had to spin up a new database server at postgresql://<username>:<password>@autorack.proxy.rlwy.net:57528/<database> and mount the volume from the old instance to the new one to be able to access the data again.
It was not a firewall issue and not something I changed on the code as it got fixed by deploying a new database server now hosted at autorack.proxy.rlwy.net .
What caused this issue? Where there any changes that made monorail.proxy.rlwy.net port 26206 not accessible on Aug 20, 2024?
4 Replies
a year ago
Hello, We had no other reports of the database connections failing so we would have to default to this being an application level issue that prevented the connection.
Either way, I'm glad you found a solution that worked for you!
Status changed to Solved brody • about 1 year ago
Status changed to Open nelsonochoam • about 1 year ago
a year ago
It was not an application-level issue, otherwise, I would have been able to connect through psql which I could not (so not an application issue). Additionally, I use db beaver (a similar tool as pgadmin) and I had my connection credentials in there which had been working from the very beginning (last 4) months and I could not connect from there either.
Do you have any idea as to why that might have happened? I was using an old database instance which I had spun up likely about 10 months ago. While I solved the issue by spinning a new database instance and connecting the volume to the new instance, I would still like to learn why this kind of thing happened.
We are gearing to upgrade our account to PRO but having these types of issues with no good answer is not a great sign, especially if we decide to host our database with Railway.
a year ago
I'm sorry but we do not have any more observability into what is happening at an application level, in this case the application is Postgres.
Perhaps Postgres offers a way to turn on debug logging?
a year ago
That is a great point, I can't find any logs related to that service anymore, but as you mentioned it could have been something got borked with Postgres (although it showed up as running in the dashboard so I did not think about looking at that specific service logs).
I will keep that in mind in case this ever happens again to us.