2 months ago
Important details:
Project ID: 49a26598-65f0-4519-95f5-8c44f060e27e
Environment: production (6a17780b-06ed-4271-9f62-47e9202fb239)
Deployment ID: c737fd0b-477d-48d4-9c58-581ed37d6a1d
Message: "Multiple services failing at CREATE_CONTAINER - infrastructure issue with container provisioning"
Railway's
in this specific environment.
Attachments
5 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 months ago
2 months ago
thats a host provisioning failure on railways side so staff will have to fix the root cause, but you dont have to wait on it: go to service settings → deploy → region and switch off US West (us-east or europe), then redeploy. these create_container failures are usually tied to one bad host/region and moving region gets you onto different hardware immediately. switch back later once theyve fixed it. also worth a glance at status.railway.com to see if us-west is flagged
manuproject
thats a host provisioning failure on railways side so staff will have to fix the root cause, but you dont have to wait on it: go to service settings → deploy → region and switch off US West (us-east or europe), then redeploy. these create_container failures are usually tied to one bad host/region and moving region gets you onto different hardware immediately. switch back later once theyve fixed it. also worth a glance at status.railway.com to see if us-west is flagged
2 months ago
Thank you for your help, but unfortunately, it still didn’t work.
andrebolero11-rgb
Thank you for your help, but unfortunately, it still didn’t work.
2 months ago
what can you see currently?
2 months ago
The image you're trying to deploy (atendai/evolution-api) is moved to evoapicloud/evolution-api, open your service settings and change the deploy source to evoapicloud/evolution-api:latest