8 months ago
Hello Railway Support,
I'm experiencing serious issues with the MySQL container on your platform.
The MySQL container takes too long to fully start, often getting stuck at the InnoDB initialization phase.
Even when it does start, during the initial minutes, any connection attempts (internal or external) fail with ECONNREFUSED, even when using the internal Railway address provided in the dashboard.
I've already confirmed that my connection string, ports, and credentials are correct.
The issue happens even when trying to connect directly from another Railway service (internal network).
4 Replies
Until recently, my MySQL service was working perfectly fine without any issues.
I haven’t made any changes to my code, configuration, environment variables, or deployment settings.
Status changed to Open chandrika • 8 months ago
7 months ago
Even though you have not changed anything, it is possible that the MySQL container is now struggling with slow InnoDB initialization or resource linit (like CPU/memory), leading to the error. I believe your app might be trying to connect before my sql is actually ready. so i think you should add a rety loop or a delay before connecting