3 months ago
Hello Railway Support Team,
I'm writing to report a persistent deployment issue that's preventing me from launching my application.
Despite trying multiple approaches, I consistently receive the same error without any build logs or detailed error information.
Issue Description:
When attempting to deploy my (private) GitHub repository (Gradius-AI/gradius-flodesk-user-sync), I immediately receive the error "There was an error deploying from source" without any build logs or additional information.
The error appears instantly after clicking "Deploy the repo" button, suggesting the issue occurs before the build process even begins.
Repository Information:
Repository: https://github.com/Gradius-AI/gradius-flodesk-user-sync
Content: A Node.js cron job application that syncs user data from PostgreSQL to Flodesk
Main files in the repo: sync.js, package.json, Dockerfile, railway.json, README.md, package-lock.json, .gitignore
I've tried the following approaches, all resulting in the same immediate error:
Fresh Repository Setup: Deleted and recreated the repository with proper configuration files
Dockerfile Implementation: Added a Dockerfile to provide explicit build instructions.
Railway Configuration: Added a railway.json file with explicit build/start commands
Start Command Configuration: Set the start command to
node sync.js
in the service settingsEnvironment Variables: Set up all required environment variables for the application
As an additional test, I even created a completely minimal test repository with only the most basic Node.js files:
Repository: https://github.com/Gradius-AI/test
Contents:
An index.js file with just a console.log and setInterval
A basic package.json with only a start script
This minimal test repository resulted in the exact same immediate error: "There was an error deploying from source" without any logs or further details.
I've also verified that the Railway GitHub App has full repository access permissions to my GitHub organization.
This strongly suggests the issue is not with my codebase but rather with something fundamental in the Railway/GitHub integration for my account or organization.
Despite all these attempts, the error remains the same - an immediate "There was an error deploying from source" with no further details or logs.
What's particularly strange is that the error appears instantly without any build logs.
For additional context, I initially used a Railway template created by developer Faraz Patankar (a Node.js cron job template) to run my integration script (sync.js). When this approach wasn't working, I attempted to delete the service. However, this template service still appears in my project dashboard with a "Service will be deleted" status and hasn't fully disappeared even after 2 days since deletion. I strongly suspect this hanging deleted service might be causing conflicts that prevent any new deployments from succeeding.
Could you please investigate:
1. Why my deployment fails before generating any logs
2. If there are any issues with my Railway account configuration
3. If the "Service will be deleted" status is causing conflicts
4. What steps I can take to successfully deploy this application
Any assistance would be greatly appreciated as this is blocking the launch of an important integration for our application and also blocking all my GitHub-based deployments.
Thank you for your help,
Eli (Railway Pro User)
Railway username: elilouise
Railway Project ID: 02ec1cf1-695a-49c7-a5a6-2edc3bbfed7d
5 Replies
3 months ago
Hello,
I see you have outstanding changes, have you tried applying them?
Best,
Brody
Status changed to Awaiting User Response railway[bot] • 3 months ago
brody
Hello,I see you have outstanding changes, have you tried applying them?Best,Brody
3 months ago
That solved it! You're the best Brody! A million thanks!!!
Status changed to Awaiting Railway Response railway[bot] • 3 months ago
Status changed to Awaiting User Response railway[bot] • 3 months ago
Status changed to Solved brody • 3 months ago
brody
Happy to help!
3 months ago
I'm having the same problem, how do I solve it?
Status changed to Awaiting Railway Response railway[bot] • 3 months ago
btukin
I'm having the same problem, how do I solve it?
3 months ago
Hi there, basically I could not deploy new services and repositories because I had not properly deleted the Node.js cron job template from the dashboard.
To delete a Node.js cron job template properly:
Click the delete button on the template
Click the blue "Deploy Changes" button to execute the deletion
Without completing both steps, the template remains in the system, preventing deployment of new services and repositories.
Status changed to Solved echohack • 3 months ago