3 months ago
I am currently unable to reach my main database. I was working in it this morning but for past 15 minutes it is unreachable
This is the URL I reach it at: https://nocodb-production-85b1.up.railway.app/#/nc/pwb93zmdhlciuxz
What I found:
Config points to https://nocodb-production-85b1.up.railway.app/.
StoryMap’s local database health endpoint says NocoDB is configured, token is present, and reachable.
Authenticated NocoDB API calls do work, but slowly: metadata calls took about 3.7s to 14.4s.
/api/v1/health sometimes returned OK, but one check timed out at 15s.
The dashboard HTML and static assets are especially sluggish. Some UI assets took 7s to 11.5s, and one page load timed out at 15s.
The NocoDB health response showed the service has been up for about 11.8 days.
My read: this is a live Railway service that has gotten sluggish or partially wedged, not a bad URL/token problem. A Railway service restart is the right first move, then check logs if it bogs down again.
2 Replies
3 months ago
Your NocoDB service in the "Storyops NocoDB" project shows a healthy deployment and the volume is at about 4.8 GB of 20 GB, so no disk pressure. Your diagnosis sounds right. You can restart the service directly from the dashboard by opening the service, clicking the three-dot menu on the active deployment, and selecting "Restart", or by pressing Cmd+K (Ctrl+K on Windows) and typing "restart" in the command palette.
Status changed to Awaiting User Response Railway • 3 months ago
Railway
Your NocoDB service in the "Storyops NocoDB" project shows a healthy deployment and the volume is at about 4.8 GB of 20 GB, so no disk pressure. Your diagnosis sounds right. You can restart the service directly from the dashboard by opening the service, clicking the three-dot menu on the active deployment, and selecting "Restart", or by pressing Cmd+K (Ctrl+K on Windows) and typing "restart" in the [command palette](https://docs.railway.com/overview/keyboard-shortcuts).
3 months ago
I restarted the service and it doesn't seem to have helped.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 3 months ago