a month ago
I had a bad credentials issue a few hours ago. It resolved itself. Now, i have this issue also. Below is the conversation with the AI agent.
Done. New deployment triggered: ebacf71f-679b-4052-abc6-5751f2dfd13c
But the webhook issue needs to be fixed so you don't have to manually deploy every time. Check GitHub webhooks and let me know what you find.
No webhook there
That's the problem. The webhook was never recreated after you fixed the auth issue.
You need to reconnect the GitHub integration in Railway to regenerate the webhook:
- Go to your Railway project → Settings → Integrations
- Find GitHub and click Disconnect
- Wait a few seconds
- Click Connect and authorise again
- This will automatically create a new webhook in your GitHub repo
Once that's done, pushes to main will trigger deployments automatically.
Only integration I see is Vercel
Then the GitHub integration isn't connected at all. That's why there's no webhook.
You need to connect GitHub to Railway:
- Go to your Railway project → Settings → Integrations
- Click Add Integration or Connect GitHub
- Authorise Railway to access your GitHub account
- Select the
Ayko-Technologies/FaithBridgeCentralrepo - This will create the webhook automatically
After that, pushes to main will trigger deployments.
There is no add integration
Then you need to go to your Railway account settings (not project settings):
- Click your profile icon (top right) → Account Settings
- Go to Integrations
- Connect GitHub there
- Then come back to your project and the GitHub integration should be available
Alternatively, try going directly to: https://railway.com/account/integrations
Done. But how do I know it will work?
Push a small change to main and watch your Railway dashboard. If a new deployment starts automatically within a few seconds, the webhook is working.
You can also verify it was created:
- Go to your GitHub repo → Settings → Webhooks
- You should see a Railway webhook there now
- Click it and check the recent deliveries—they should show successful (green checkmarks)
If you push and nothing happens after 30 seconds, the webhook still isn't firing. Let me know and we'll debug further.
2 Replies
a month ago
The GitHub repo connection for auto-deploys is configured per service, not at the project level. Go to your service's Settings tab and under the Source section, connect your GitHub repo and select the branch you want to trigger deployments from. You can verify it's working by pushing a commit and checking if a new deployment appears, or by looking for a webhook under your GitHub repo's Settings > Webhooks.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Awaiting Railway Response Railway • about 1 month ago
Railway
The GitHub repo connection for auto-deploys is configured per service, not at the project level. Go to your service's **Settings** tab and under the **Source** section, connect your GitHub repo and select the branch you want to trigger deployments from. You can verify it's working by pushing a commit and checking if a new deployment appears, or by looking for a webhook under your GitHub repo's Settings > Webhooks.
a month ago
This has already been done and was done multiple times.
Status changed to Open Railway • about 1 month ago