Webhook deliveries are not being received despite successful configuration

[AbdullahNaseemAbbasi]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

API

Body

Hello everyone,

I'm having an issue with GitHub Webhooks. I've configured a webhook for my repository, but the endpoint is not receiving any events when repository activity occurs.

Environment
GitHub Webhooks
Public repository
Custom HTTPS endpoint
Windows 11
Problem

I created a webhook and configured it to send push and pull_request events to my endpoint.

The webhook configuration was saved successfully, but when I push commits or open a pull request, my server doesn't receive any requests.

What I've checked
The webhook URL is accessible over HTTPS.
The endpoint returns a 200 OK response when tested manually.
The selected events are correct.
The webhook secret matches the one configured on my server.
My firewall is not blocking incoming requests.

Despite these checks, no webhook events appear to reach my application.

[daniyal-debug]

The first place to check is the Recent Deliveries section of your webhook configuration. It will show whether GitHub attempted to send the event and, if so, the HTTP status code and response received from your server.

A few common causes include:

The selected event type doesn't match the action you're performing (for example, only listening for push events while testing with an issue or release).
The endpoint returns an error or takes too long to respond. GitHub expects a timely response and may mark the delivery as failed.
SSL or certificate issues prevent GitHub from connecting to the endpoint.
The webhook secret validation on your server is rejecting the request because the signatures don't match.
Network rules, proxies, or firewalls are preventing GitHub from reaching your server.

If GitHub isn't showing any delivery attempts, verify that the webhook is enabled and attached to the correct repository or organization. If deliveries are listed but failing, the response details in the delivery log usually provide enough information to identify the problem.

If you're still unable to determine the cause, sharing the delivery status, HTTP response code, and any relevant server logs (with sensitive information removed) would help the community troubleshoot the issue.