a month ago
Hello Railway Support,
I need urgent help restoring my production service.
Project: pacific-nurturing
Environment: production
Service: evolution-api
Public URL: evolution-api-production-615f.up.railway.app
Image: atendai/evolution-api:v1.8.6
Configuration: single replica in sfo, public domain on port 8080, no volumes.
The service was previously working normally and is required for a production WhatsApp integration.
Now every deployment fails at:
Deploy > Create container
Error: Failed to create deployment
Diagnosis: Infrastructure Error
Railway diagnosis says the deployment failed at Railway’s internal container creation step, before the image was pulled or any application code ran.
There are no application logs because the container is not being created.
Failed deployment IDs:
- 08dba27b-0a87-4e36-876c-57b0f64d633c
- 7e4c3fb3-12d8-4dcf-aadf-ba6b8f0977c1
- c73f3263-36ad-47cc-8e4e-0c7bbd1f5cb9
The same image and configuration deployed successfully before.
Please investigate the infrastructure/container creation issue and help bring the evolution-api service back online.
2 Replies
a month ago
This is blocking a production WhatsApp integration.
The CRM service is online, but the evolution-api service is offline because Railway cannot create the container.
The issue is not in the application code because the failure happens before image pull or app execution.
Please prioritize this service restoration. We need the evolution-api service back online as soon as possible.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
All three deployments failed because the Docker image atendai/evolution-api:v1.8.6 could not be pulled from Docker Hub. The repository appears to have been removed or made private by its maintainer, which is why the "create container" step fails before any application code runs. The Evolution API project may have moved the image to a different Docker Hub organization or registry since your last successful deploy, so you'll want to check the project's current documentation for the correct image reference and update it in your service settings.
Status changed to Awaiting User Response Railway • about 1 month 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 1 month ago