Description: Service: evolution-api Project: humble-manifestation Region: sfo Image: atendai/evolution-api:v1.8.7 Problem: 7+ consecutive deployments failing since July 3rd - Error: "Failed to create deployment" at CREATE_CONTAINER stage - Last successful deployment: June 24th (still running) - No configuration or image changes since then - No build/deploy logs generated What I've tried: - Multiple redeploy attempts - Reverted AUTHENTICATION_API_KEY to original value - Changed AUTHENTICATION_API_KEY to different values - All fail identically This is clearly a Railway infrastructure issue.

Container creation failing for evolution-api since July 3rd

ramon-bg

FREEOP

3 months ago

Description:

Service: evolution-api

Project: humble-manifestation

Region: sfo

Image: atendai/evolution-api:v1.8.7

Problem: 7+ consecutive deployments failing since July 3rd

Error: "Failed to create deployment" at CREATE_CONTAINER stage
Last successful deployment: June 24th (still running)
No configuration or image changes since then
No build/deploy logs generated

What I've tried:

Multiple redeploy attempts
Reverted AUTHENTICATION_API_KEY to original value
Changed AUTHENTICATION_API_KEY to different values
All fail identically

This is clearly a Railway infrastructure issue.

Solved$10 Bounty

Pinned Solution

mayori

MODERATOR

3 months ago

I take a look on other threads hours ago and the mod says that the image is moved to evoapicloud/evolution-api, try change the docker source with this new image

The reason why theres no errors from build and deploy logs is probably because it is failed to pull the image which is now moved

11 Replies

Railway

BOT

3 months ago

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

Status changed to Open Railway • 3 months ago

mayori

MODERATOR

3 months ago

are there any error messages from build or deploy logs?

mayori

are there any error messages from build or deploy logs?

ramon-bg

FREEOP

3 months ago

No, there are no error messages in either build or deploy logs. Both are completely empty. The failure happens at the CREATE_CONTAINER stage before the container even starts, so no logs are generated at all.

This confirms it's an infrastructure-level issue — the Railway system cannot even attempt to create the container for this deployment.

mayori

MODERATOR

3 months ago

I take a look on other threads hours ago and the mod says that the image is moved to evoapicloud/evolution-api, try change the docker source with this new image

The reason why theres no errors from build and deploy logs is probably because it is failed to pull the image which is now moved

mayori

I take a look on other threads hours ago and the mod says that the image is moved to `evoapicloud/evolution-api`, try change the docker source with this new image The reason why theres no errors from build and deploy logs is probably because it is failed to pull the image which is now moved

ramon-bg

FREEOP

3 months ago

I found that the image was moved from atendai/evolution-api to evoapicloud/evolution-api. I've updated the source image to evoapicloud/evolution-api:v1.8.7 and triggered a redeploy.

However, the deployment still failed at CREATE_CONTAINER stage with the same error. The service configuration now shows the correct new image (evoapicloud/evolution-api:v1.8.7), but the system is still trying to use the old one (atendai/evolution-api:v1.8.7).

This suggests there may be a caching or synchronization issue on Railway's side, or the new image repository is also inaccessible for some reason.

Deployment ID: 8dce7c5a-b500-44fe-9d71-553833571f54

mayori

MODERATOR

3 months ago

You can disable the cache by adding NO_CACHE=1 to the service variables

mayori

You can disable the cache by adding `NO_CACHE=1` to the service variables

ramon-bg

FREEOP

3 months ago

I added NO_CACHE=1 to the service variables and triggered a redeploy, but it still failed at CREATE_CONTAINER stage.

The service configuration shows the correct new image (evoapicloud/evolution-api:v1.8.7), but the deployment is still trying to use the old image (atendai/evolution-api:v1.8.7). Even with cache disabled, this isn't picking up the new configuration.

Deployment ID: bd23e4fa-4046-4a7b-a280-1e781345664f

This seems like a deeper synchronization issue on Railway's infrastructure.

mayori

MODERATOR

3 months ago

can you share the screenshot of deploy logs from your latest deployment?

mayori

MODERATOR

3 months ago

Try redeploy source image maybe? open the command palette (Ctrl+K) and select "Redeploy source image", this should pull the image

ramon-bg

FREEOP

3 months ago

There are no deploy logs at all. The logs are completely empty. The failure happens at the CREATE_CONTAINER stage, so no logs are generated before the container creation fails.

Deployment ID: bd23e4fa-4046-4a7b-a280-1e781345664f

mayori

MODERATOR

3 months ago

Try redeploy source image, usually this will pull the fetch image

mayori

Try redeploy source image, usually this will pull the fetch image

ramon-bg

FREEOP

3 months ago

Thank you! The redeploy worked perfectly. The deployment is now successful.

Status: SUCCESS

SNAPSHOT_CODE: ✅ completed
CREATE_CONTAINER: ✅ completed
CONFIGURE_NETWORK: ✅ completed
DRAIN_INSTANCES: ✅ completed

The evolution-api service is now running with the correct image (evoapicloud/evolution-api:v1.8.7).

Deployment ID: ccc4e561-53f3-456f-b543-2a446ab4fd56

Status changed to Solved medim • 3 months ago

Welcome!