12 days ago
I'm trying to deploy a new service in project "artistic-cooperation" from a
private GitHub repo (massardfreeagents/mailing-forexperts), using a
subdirectory ("webhook") as Root Directory.
Every deploy attempt fails immediately with the toast message "There was an
error deploying from source." No build logs or deploy logs are generated at
all -- the Deployments tab goes straight back to "There is no active
deployment for this service."
What I've already checked/tried:
-
Confirmed the repo content is correct in that subdirectory
-
Confirmed Root Directory is set correctly
-
Confirmed Source Repo and branch (main) are correctly linked
-
Disconnected and reconnected the repo in Railway
-
Deleted the service entirely and recreated it from scratch (same result)
-
Verified in github.com/settings/installations that the Railway GitHub App
has explicit access to this repo (private, listed under "Only select
repositories")
-
Removed and re-added the repo from the GitHub App's repository access
list to force re-issuing permissions
-
Checked status.railway.com -- shows "Fully Operational", no active
incidents
-
Checked account usage -- well within Hobby plan limits
Another service in the same project, deploying from a different repo,
works fine -- so the account/project itself isn't blocked.
I found a very similar report on this forum: "Railway fails to build with
no reason nor logs - There was an error deploying from source" (marked
Solved, but the only resolution was the issue disappearing on its own
after ~9 hours). I'm hitting the exact same symptoms.
Could you check the internal deploy logs for this attempt on your end?
Project: artistic-cooperation
Repo: massardfreeagents/mailing-forexperts
Root Directory: webhook
Note: I selected "Postgres" in the service field above just to link this
ticket to the correct project (artistic-cooperation), since the actual
failing deploy never produced a service with a successful deployment to
select from the list.
1 Replies
12 days ago
The service "mailing-forexperts" and its configuration (repo, branch, root directory, variables) are sitting in your environment's staged changeset and have never been applied. You should see a bar at the top of your project canvas showing pending changes with a Deploy button. Clicking Deploy there will commit the service creation and trigger the first build. Until that staged changeset is applied, no deployment can start, which is why you see no logs.
Status changed to Awaiting User Response Railway • 12 days ago
4 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 • 4 days ago