GitLab webhook not working: "Temporarily disabled", blocked URLs and fixes
Short answer
Start in Settings › Webhooks › Edit › Recent events, which lists every request from the last two days with its status code. On GitLab.com, GitLab temporarily disables a project or group webhook after four failures in a row, starting at one minute and growing to 24 hours, and disables it until you re-enable it after 40; a test that returns a 2xx status turns it back on. A failure is a 4xx or 5xx response, a timeout, or another HTTP error, and GitLab.com waits only 10 seconds, so the receiver should reply 200 at once and do the work later. On GitLab Self-Managed, a webhook to a private address fails with "Requests to the local network are not allowed" until an administrator allows it.
Your CI server, chat bot or deploy script stopped hearing from GitLab, and the webhook in Settings › Webhooks shows Temporarily disabled or Disabled, or nothing at all looks wrong. Here’s how to find the cause in GitLab 19.5.
Start with Recent events
With the Maintainer or Owner role in the project, or Owner in the group for a group webhook:
- Go to Settings › Webhooks and select Edit for the webhook.
- Scroll to Recent events. It lists every request from the last two days: green for 2xx status codes, red for others, and
internal errorwhen GitLab couldn’t deliver at all. - Select View details to see the request GitLab sent and the response it got. Resend Request sends it again.
No events at all means GitLab never triggered the webhook: see not triggered.
“Temporarily disabled” and “Disabled”
GitLab counts a request as failed when the receiver returns a 4xx or 5xx status, doesn’t answer in time, or hits another HTTP error.
- After 4 failures in a row, the webhook shows Temporarily disabled. It’s paused for one minute, longer after each further failure, up to 24 hours, then turned back on automatically.
- After 40 failures in a row, it shows Disabled and stays off.
- To turn it back on, fix the receiver, then choose an event from the webhook’s Test dropdown. A 2xx response re-enables it.
This applies to project and group webhooks on GitLab.com. On GitLab Self-Managed, it’s behind the auto_disabling_web_hooks feature flag, which is off by default. Before GitLab 17.11, the labels read Failing to connect and Fails to connect.
The receiver is too slow
GitLab.com waits 10 seconds for a response, and each timeout counts as a failure. A receiver that runs a build or a deploy before answering fails every time.
- Reply with
200or201at once, and process the event in a queue. - Expect duplicates. The same event can arrive more than once, for example when someone resends it. The
webhook-idheader stays the same, so deduplicate on it. - Return 4xx only for a misconfigured webhook, and avoid
500for events you’ve handled: both count as failures.
On GitLab Self-Managed, an administrator sets the timeout with gitlab_rails['webhook_timeout'] in gitlab.rb.
The URL is blocked
Url is blocked: Requests to the local network are not allowed
GitLab refuses webhooks to private addresses, such as 10.x, 172.16.x and 192.168.x, so that a webhook can’t reach internal services. localhost, loopback addresses and the GitLab server’s own addresses get their own messages, such as “Requests to localhost are not allowed”.
- On GitLab Self-Managed, an administrator goes to Admin › Settings › Network, expands Outbound requests, and selects Allow requests to the local network from webhooks and integrations, or adds only the receiver’s address to the allowlist there.
- On GitLab.com, webhooks can’t reach a private network: give the receiver a public HTTPS address.
The receiver rejects the request
- 401 or 403: the receiver checks a token. GitLab sends the Secret token as plain text in the
X-Gitlab-Tokenheader, or, with a Signing token, an HMAC signature inwebhook-signature, available since GitLab 19.0. Check that both sides use the same token. unable to get local issuer certificate: GitLab can’t verify the receiver’s certificate, usually because of a missing intermediate certificate, or a certificate authority that GitLab doesn’t trust. Fix the certificate rather than turning off Enable SSL verification.
Not triggered at all
- The trigger isn’t selected, or a branch filter on Push events excludes your branch.
- A push that changes more than three branches, or more than three tags, at once sends no push or tag push webhooks for them. On GitLab Self-Managed, an administrator can raise the limit.
- The rate limit, on GitLab.com. All webhooks in a top-level namespace share a per-minute limit, 500 calls on Free. Calls over it are dropped, not sent later, until the next minute, and the webhook shows a badge.
- Silent Mode, on GitLab Self-Managed, stops project, group and system webhooks.
On your phone
MergeBell’s alerts don’t depend on your own webhooks: they come from regular checks of your to-dos, every five minutes on the free tier or every minute on Pro. Pro’s Instant mode adds a project webhook of its own as a doorbell, for alerts within seconds. Webhook settings and Recent events need GitLab in a browser. More on alerts in GitLab push notifications on your phone.
Frequently asked questions
Why is my GitLab webhook "Temporarily disabled"?
It failed four times in a row: the receiver returned a 4xx or 5xx status, timed out, or the request hit another HTTP error. GitLab pauses it for one minute, longer after each further failure, up to 24 hours, then turns it back on. After 40 failures in a row it shows Disabled and stays off. Fix the receiver, then send a test from the Test dropdown: a 2xx response re-enables it.
How do I re-enable a disabled GitLab webhook?
Fix what made it fail, then go to Settings › Webhooks and choose an event from the webhook's Test dropdown. If the receiver answers with a 2xx status, GitLab turns the webhook back on. You need the Maintainer or Owner role for a project webhook, or the Owner role for a group webhook.
What timeout does a GitLab webhook have?
GitLab.com waits 10 seconds for a response. A slower receiver counts as failed, and repeated timeouts get the webhook disabled. Reply with 200 straight away and process the event in a queue. On GitLab Self-Managed, an administrator sets the timeout with webhook_timeout in gitlab.rb.
Why does GitLab say "Requests to the local network are not allowed" for a webhook?
GitLab blocks webhooks to private addresses, such as 10.x, 172.16.x and 192.168.x, so they can't reach internal services. On GitLab Self-Managed, an administrator allows them in Admin › Settings › Network › Outbound requests. GitLab.com can't reach your private network at all: expose the receiver on a public address.
Why isn't my GitLab webhook triggered at all?
Check that the webhook isn't disabled and that its trigger, such as Push events, is selected, with no branch filter that excludes your branch. By default, a push that changes more than three branches, or more than three tags, at once sends no push webhooks for them. On GitLab.com, calls over the namespace's per-minute rate limit are dropped until the next minute.
Sources
- GitLab docs — Webhooks: auto-disabled webhooks
- GitLab docs — Webhook receiver requirements
- GitLab docs — Troubleshooting webhooks
- GitLab docs — GitLab.com webhook limits
- GitLab docs — Allow requests to the local network from webhooks
- GitLab source — webhook auto-disabling (auto_disabling.rb)
Checked against these pages on 7 November 2026. GitLab changes quickly — if something here no longer matches, tell us and we will fix it.
Do this from your phone with MergeBell
Free for the whole review loop: the To-Do inbox, diffs and line comments, approve and merge, pipelines with retry, and push alerts for your To-Dos. Works with gitlab.com and self-managed GitLab 16.0+.
Get MergeBell for iPhoneGet MergeBell for Android
On the App Store for iOS 26 or later and on Google Play for Android 12 or later. An independent app, not affiliated with GitLab Inc.