a month ago
Hi Railway team,
I'm experiencing a persistent deployment failure and need help investigating the root cause.
Account: pizichina (Hobby Plan)
Project: outstanding-tranquility
Service: eivf-platform-template
GitHub Repo: pizichina/eivf-platform-template (private)
Branch: master
Issue:
Every deployment attempt fails instantly with "There was an error deploying from source." There are zero build logs generated — the failure happens before any build step runs.
What I've tried:
- Railpack builder → same error
- Nixpacks builder → same error
- Dockerfile builder → same error
- Set custom build command manually in UI → same error
- Disconnected and reconnected GitHub integration → same error
- Deleted the service and created a brand new one → same error
- Verified Railway App has correct GitHub permissions (read/write on the repo)
- Verified billing is fine ($5.00 credits available, current usage $0.00)
- Railway status page shows Fully Operational
Since the failure is instant with no logs across all builder types, even after recreating the service, I suspect there may be something on the backend (account, repo, or service level) that is blocking the deployment from starting. Could you please check the server-side logs for this service?
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hi there,
I investigated the backend logs and found the root cause. When you attempted to deploy on April 10th, the error was:
Free plan resource provision limit exceeded. Please upgrade to provision more resources!
This explains the instant failure with no build logs - the deploy was blocked before any build could start because of Free plan resource limits. Unfortunately, the frontend displayed a generic "error deploying from source" message instead of surfacing this specific error, which made it confusing to diagnose.
I can see you've since upgraded to Hobby and have been successfully deploying to your "Jacobae" project. So it looks like you're all set now.
Apologies for the confusing error message - I'll flag this internally as a UX issue since the actual error should have been shown to you directly.
Let me know if you have any other questions!
Status changed to Awaiting User Response Railway • 27 days ago
20 days 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 • 20 days ago