Subject: Deployment misconfiguration after balance depletion — need rollback to previous working setup
numno4bka
HOBBYOP

8 months ago

Hello Railway Support Team, I hope you're doing well. I'm reaching out because my project deployment got completely misconfigured after my account ran out of funds. Prior to that, everything was working perfectly. Specifically: My project had a main service (server.js, redisClient.js, webpack.config.js) which was built using railway.toml. I also had a separate Docker-based worker (imageWorker.js, queueRedisClient.js) using railway.imageWorker.toml with its own Dockerfile. Redis and MySQL were connected as Railway-managed services, and everything was properly isolated. After the billing issue, it seems that the services got mixed up: redisClient.js and MySQL are now being bundled or deployed through the Docker container meant only for imageWorker. The image worker logic seems to be building via webpack.config.js, which should never happen. Please help me restore the configuration exactly as it was yesterday, with: The Million USDT Artwork service built via npm run build using railway.toml ImageWorker deployed via its own Dockerfile using railway.imageWorker.toml Proper service isolation as before. Let me know if you need project ID or deployment references. Thanks a lot in advance!

Solved

2 Replies

numno4bka
HOBBYOP

8 months ago

All good, I figured it out and rolled back the changes. Thank you


numno4bka

All good, I figured it out and rolled back the changes. Thank you

8 months ago

Hey, I am glad that you have solved your issue this quick, I'll go ahead and mark this thread as solved.


Status changed to Solved uxuz 9 months ago


Loading...