GitHub webhooks not re-registered after account restore from free tier
karanwasabi
PROOP

2 hours ago

My account temporarily downgraded to free tier when a payment failed to auto-debit today. I've since restored access to a paid pro account within a short time.

However, GitHub auto-deploy webhooks were removed during the downgrade and have not been re-registered, despite the account being restored to paid tier.

What I've tried:

Disabled and re-enabled auto-deploy on the sbm-backend service

Checked GitHub webhook settings — the webhooks list is now empty (no webhooks from api.railway.app exist)

Result: Git pushes to the main branch are no longer triggering automatic deployments.

Project details:

Project ID: db670d5d-8bec-4b43-bc29-e0a4fce2fdd8

Environment: production (69c270da-9be3-4f15-b060-716ae334cfb9)

Service ID: 5323004d-b111-4ce6-be64-b7ca2ff9051c (sbm-backend)

Repository: karanwasabi/sbm-backend

Branch: main

Request: Please re-register the GitHub webhook for this service so that auto-deploy works again when I push commits to the main branch.

Solved$20 Bounty

3 Replies

Railway
BOT

2 hours ago

Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.

This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

  • Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
  • Keep it private and close the thread - Nothing becomes public. The thread closes, since this isn't something Railway support can take further.

Status changed to Awaiting User Response Railway about 2 hours ago


karanwasabi
PROOP

2 hours ago

Railway bot has put the blame on configuration from my end instead of resolving it. So now it seems its open to the community. Please help me restore the webhook in GitHub to have the auto deployments work smoothly.


Railway
BOT

2 hours ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway about 2 hours ago


Status changed to Awaiting Railway Response Railway about 2 hours ago


karanwasabi
PROOP

an hour ago

I resolved it on my own. I disconnected the repository from the project settings source repo. then refreshed. then added it again. auto deploy on push is working again


Status changed to Solved Railway about 1 hour ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...