2 months ago
Evolution API failing to deploy after trial upgrade — Infrastructure Error
After upgrading from the trial plan, my evolution-api service is failing to deploy with "Failed to create deployment" at the container creation stage. No logs are generated, the container never starts.
The Railway diagnosis identified this as a transient infrastructure error, but the issue persists after multiple redeploy attempts.
- Image: atendai/evolution-api:v1.8.7 (Docker Hub)
- Region: US West
- Deployment ID: 17b8fe01
Postgres and Redis in the same project came back online without issues. Same image and config worked fine before the trial expired.
Has anyone seen this after reactivating a plan?
Attachments
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Your deployments are failing because the Docker Hub image atendai/evolution-api:v1.8.7 cannot be pulled. Please verify that this tag still exists on Docker Hub - image maintainers sometimes remove older tags. If the tag is still available, try using the command palette (Cmd/Ctrl + K) and selecting "Redeploy source image" to force a fresh pull. If the tag has been removed, update your service's image reference to a current tag.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 2 months ago