a month ago
Title: Container creation failing within 1 second — infrastructure error confirmed by Diagnose tool
I'm unable to deploy a Docker image service. The deployment fails at "Deploy > Create container" in under 1 second, with no logs generated, across 10+ attempts in multiple regions (US West and EU West).
The built-in Diagnose tool confirmed: "All user-side causes have been ruled out, so the Railway team should investigate."
Service ID:
3b83aded-b0be-4141-a45e-5a3ee85828a9Deployment ID:
791c4f0b-74ed-43d9-805b-d6413fc8613aImage:
atendai/evolution-api:latestError: Failed to create deployment
Railway support suggested posting here with these IDs for the team to investigate the orchestration logs. Please advise or process a refund if this cannot be resolved.
Pinned Solution
a month ago
Sorry, I'm only a Railway Community member. Not Railway Staff. However, I do know that Railway's Fair Use policy (https://railway.com/legal/acceptable-use) forbids "running bots or scrapers that violate applicable terms of service" and that you may not use it "to send unsolicited bulk messages through any communication channel". You can try to go to your workspace billing page (https://railway.com/workspace/billing) and Request Refund or Cancel Plan there.
If your question has been answered, please mark my solution as the accepted solution so the thread can close properly. Thanks!
6 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Hey! I took a look at this and It's not an infrastructure bug. According to Railway Staff, WhatsApp bots are not allowed on Railway. As a result, you cannot host Evolution API (https://station.railway.com/questions/evolution-api-deploy-error-d20f9cda)
You will likely need to find another platform to host your bot.
a month ago
Thank you for the clarification. However, this policy was never communicated during the sign-up process or at any point before I upgraded to the Hobby plan. I paid specifically to host this service, and it was blocked without any clear error message — only a generic "Failed to create deployment" that even Railway's own Diagnose tool misidentified as an infrastructure scheduling issue.
Since the service I paid for cannot be used due to an undisclosed platform restriction, I'm requesting a full refund of my Hobby plan subscription.
Please advise on how to proceed with the refund.
a month ago
Sorry, I'm only a Railway Community member. Not Railway Staff. However, I do know that Railway's Fair Use policy (https://railway.com/legal/acceptable-use) forbids "running bots or scrapers that violate applicable terms of service" and that you may not use it "to send unsolicited bulk messages through any communication channel". You can try to go to your workspace billing page (https://railway.com/workspace/billing) and Request Refund or Cancel Plan there.
If your question has been answered, please mark my solution as the accepted solution so the thread can close properly. Thanks!
wtesoares-oss
> Thank you for the clarification. However, this policy was never communicated during the sign-up process or at any point before I upgraded to the Hobby plan. I paid specifically to host this service, and it was blocked without any clear error message — only a generic "Failed to create deployment" that even Railway's own Diagnose tool misidentified as an infrastructure scheduling issue. > > Since the service I paid for cannot be used due to an undisclosed platform restriction, I'm requesting a **full refund** of my Hobby plan subscription. > > Please advise on how to proceed with the refund.
a month ago
You can go to your workspace billing page and Request Refund n that page
Status changed to Solved dev • about 1 month ago
a month ago
Hey, the provided solution is wrong.
Just change the source image to evoapicloud/evolution-api:latest
Status changed to Awaiting Conductor Response Railway • about 1 month ago
Status changed to Solved medim • about 1 month ago