2 months ago
My GitHub-connected services cannot deploy.
The integration intermittently shows either:
- Bad credentials
- Auto deploy unavailable
When I manually select Deploy Latest Commit, it fails with: Failed to trigger deployment. Problem processing request
I have already:
- Logged out and reauthenticated with GitHub
- Revoked and reauthorized Railway’s OAuth access
- Uninstalled and reinstalled the Railway GitHub App
- Confirmed the app has explicit repository access
- Disconnected and reconnected the repository sources
- Refreshed Railway’s repository list
- Waited for permissions and caches to propagate
I have administrator access to the repositories, and the configured branches exist. The problem persists across connected services.
4 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
I can now trigger manual deployments but connected branch still shows up as "Auto deploy unavailable".
2 months ago
Thanks for the detailed list, you have already done everything on your side correctly, so this is not your configuration. The "Auto deploy unavailable" state you are still seeing is a known platform-side condition with the GitHub connection, and it needs to be re-registered server-side. We can do that for you.
In the meantime, manual Deploy Latest Commit (which you confirmed is working again) will keep pushing your latest code while we fix auto deploy.
To target this precisely, can you confirm the GitHub repository (owner/repo) and the exact service that should auto deploy? Once we have that we will re-register the connection and auto deploy will come back online.
Status changed to Awaiting User Response Railway • 2 months ago
angelo-railway
Thanks for the detailed list, you have already done everything on your side correctly, so this is not your configuration. The "Auto deploy unavailable" state you are still seeing is a known platform-side condition with the GitHub connection, and it needs to be re-registered server-side. We can do that for you. In the meantime, manual Deploy Latest Commit (which you confirmed is working again) will keep pushing your latest code while we fix auto deploy. To target this precisely, can you confirm the GitHub repository (owner/repo) and the exact service that should auto deploy? Once we have that we will re-register the connection and auto deploy will come back online.
2 months ago
Thanks for the reply, the GitHub repositories and service are:
bob-the-builder-v2/a-tiny-erp-backend:Backendbob-the-builder-v2/civil-servant-backend:civil-servant-backend
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Thanks, that gives us the targets.
We have the affected repo/service pairs as:
bob-the-builder-v2/a-tiny-erp-backend->Backendbob-the-builder-v2/civil-servant-backend->civil-servant-backend
Manual deploys working while auto deploy shows unavailable points to the GitHub deployment trigger/webhook registration rather than your repo permissions. The remaining fix is on our side: refresh/re-register the GitHub connection for those service sources so branch auto-deploys are available again. We will follow up once that is done.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months 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 2 months ago