[Help!] Core service crash for my company...
rendercoder
PROOP

17 days ago

I have a Node.js program running on Railway.

Just now, it gave me a message saying it couldn't connect to the database, which is very unusual. I'm actually connecting to a paid Supabase resource. I'm using a database client locally, and Supabase works fine. I'm pretty sure the problem is with the Railway platform.

Here is log:


SequelizeConnectionError: connect ETIMEDOUT 3.0.121.111:5432 at Client._connectionCallback (/opt/outline/node_modules/sequelize/lib/dialects/postgres/connection-manager.js:145:24) at Client._handleErrorWhileConnecting (/opt/outline/node_modules/pg/lib/client.js:379:19) at Client._handleErrorEvent (/opt/outline/node_modules/pg/lib/client.js:389:19) at Connection.emit (node:events:509:28) at Connection.emit (node:domain:489:12) at Socket.reportStreamError (/opt/outline/node_modules/pg/lib/connection.js:56:12) at Socket.emit (node:events:509:28) at Socket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at process.processTicksAndRejections (node:internal/process/task_queues:90:21)

Strangely, in the same service area, my other services also connect to the Supabase service without any problems. I've confirmed it's not a problem on my end; my services have been running stably for over two years.

Please fix this issue immediately and help me troubleshoot it—I’m really at my breaking point… This is a core internal collaboration service for the company, and we’re still in working hours!

Solved$20 Bounty

2 Replies

Railway
BOT

17 days ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway 17 days ago


rendercoder
PROOP

17 days ago

Project ID: 028f59e8-895a-40ed-bd82-05a25a81146c


Status changed to Solved rendercoder 17 days ago


rendercoder
PROOP

17 days ago

The issue has been resolved. I didn’t do anything—looks like the platform fixed it?


Status changed to Awaiting Railway Response Railway 17 days ago


Status changed to Solved rendercoder 17 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...