a month ago
Hello,
I'm experiencing a critical issue on my Railway project "thorough-flexibility" (service: devlikeapro/waha).
PROBLEM:
Every deployment of a private Docker image gets stuck in QUEUED status with the message "Waiting for previous deployment" — even when there is NO previous deployment running. The deployment never starts pulling or initializing.
CONTEXT:
- Service ID/URL: devlikeaprowaha-production-3a12.up.railway.app
- Region: EU West
- I'm pulling a private image from Docker Hub: devlikeapro/waha-plus:latest
- My Docker Hub PAT is valid and I confirmed it has read access to the image (verified via direct API call: HTTP 200 on the manifest endpoint)
- The format I use in Source Image: username:PAT@image (devlikeapro:dckr_pat_***@devlikeapro/waha-plus:latest)
WHAT I'VE TRIED:
- Multiple Source Image URL formats (with and without :latest, with :amd64)
- Disconnect + reconnect the source via "Connect Image"
- Remove all previous deployments (history all REMOVED)
- Clicked "Deploy the image" link on empty deployments page
- One deployment briefly went to INITIALIZING / "Pulling image..." then went back to QUEUED "Waiting for previous deployment" — even though no previous was running
The CORE/public image (devlikeapro/waha:latest, no auth) works perfectly — it's only the private image that triggers this issue.
Can you please investigate why the queue is stuck on this service?
Thank you!
1 Replies
a month ago
Private registry credentials are a Pro plan feature, and your workspace is currently on the Hobby plan. This is why deployments of the private image get stuck while the public image works fine. To deploy from a private Docker registry, you would need to upgrade to Pro, then configure your credentials through the service's Settings page under "Registry Credentials" rather than embedding them in the image URL.
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 • 29 days ago