Deployment fails at "Create container" step with no logs — evolution-api
mariayossimi
HOBBYOP

6 days 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.

$10 Bounty

1 Replies

Railway
BOT

6 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 6 days ago


6 days 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


Welcome!

Sign in to your Railway account to join the conversation.

Loading...