2 months ago
The evolution-api service deployment fails instantly at the "Deploy › Create container" step (00:00), with no logs in either Build Logs or Deploy Logs. I tried upgrading from v2.1.1 to v2.2.3, and also tried redeploying the same v2.1.1 — both fail the same way. The automatic "Diagnose" tool also returned "Diagnosis failed for this deployment." Deployment IDs: f5a123ea (failed trying v2.2.3), bcb68878 (failed trying v2.1.1). I already checked and it's not a billing/spending limit issue on the account — I recently deleted an unused duplicate project to free up resources, but the issue persists.
4 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
Usually the error occurred because the image is moved to evoapicloud/evolution-api and you're still using atendai/evolution-api
Change your Deploy Source to evoapicloud/evolution-api:v2.2.3
a month ago
Thanks for the update. I’m seeing 'Failed to create deployment at Create Container' with no logs. Railway suggests checking DockerDocker image 'nexova.' I’m not sure why it’s using that image. Could you please check whether my deploy source is misconfigured and tell me the correct fix? Thank youyou
a month ago
This issue happens before the container even initializes because Railway fails to pull the specified image from Docker Hub. If the repository name or tag is outdated, misspelled (like the nexova reference), or pointing to the legacy namespace, the orchestrator aborts immediately at 00:00 without generating runtime logs.
Steps to Resolve
Update the Image Source:
- Go to your service Settings tab in Railway.
- Under the Source Image / Deploy section, click Edit.
- Replace the existing image path with the current official repository:
evoapicloud/evolution-api:v2.2.3 (or evoapicloud/evolution-api:latest).
Clear Custom Start Commands:
Ensure the Custom Start Command under Deploy settings is completely empty so it defaults to the image entrypoint.
Verify Port Configuration:
Check that PORT under your service Variables is set to 8080 (Evolution API default).
Trigger a Clean Redeploy:
Hit Redeploy or trigger a new deployment via the service overview.
coffeeai-au
This issue happens before the container even initializes because Railway fails to pull the specified image from Docker Hub. If the repository name or tag is outdated, misspelled (like the nexova reference), or pointing to the legacy namespace, the orchestrator aborts immediately at 00:00 without generating runtime logs. Steps to Resolve Update the Image Source: 1. Go to your service Settings tab in Railway. 2. Under the Source Image / Deploy section, click Edit. 3. Replace the existing image path with the current official repository: evoapicloud/evolution-api:v2.2.3 (or evoapicloud/evolution-api:latest). Clear Custom Start Commands: Ensure the Custom Start Command under Deploy settings is completely empty so it defaults to the image entrypoint. Verify Port Configuration: Check that PORT under your service Variables is set to 8080 (Evolution API default). Trigger a Clean Redeploy: Hit Redeploy or trigger a new deployment via the service overview.
a month ago
let me know the outcome