Webhooks not working

[Thunderrock424242]

My webhook from my repository to discord won't work. Is there something wrong that git hub is working on? I will send the error that it gives me soon

[queenofcorgis]

Welcome to the GitHub Community, @Thunderrock424242 , we're happy you're here! You are more likely to get a useful response if you are posting your question in the applicable category. I've gone ahead and moved it for you. Good luck!

[Thunderrock424242]

My webhook from my repository to discord won't work. Is there something wrong that git hub is working on? I will send the error that it gives me soon

log from the web hook

Alt-Svc: h3=":443"; ma=86400
Cf-Cache-Status: DYNAMIC
Cf-Ray: 7f7d04e32c6a3818-IAD
Content-Length: 45
Content-Security-Policy: frame-ancestors 'none'; default-src 'none'
Content-Type: application/json
Date: Wed, 16 Aug 2023 22:12:29 GMT
Nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Report-To: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v3?s=gTaMzFOlJ1f7sK1IO8xrE%2FPrW%2B23soNEzysGFhOIeRdIcRqKLFpSah%2BIp2A7BOZsJINNFML2fhTeyyvXkyMQp0NUEyr1djLJl1GM%2FStco8sfJzVx6J6JXtTCM3%2Bh"}],"group":"cf-nel","max_age":604800}
Server: cloudflare
Set-Cookie: __dcfduid=fd5215243c8111ee98f4aae8ad09bf84; Expires=Mon, 14-Aug-2028 22:12:29 GMT; Max-Age=157680000; Secure; HttpOnly; Path=/
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Via: 1.1 google
X-Content-Type-Options: nosniff
Body
{"message": "Unknown Webhook", "code": 10015}

[Yash-Dobariya]

This error typically occurs when the webhook URL you've provided to Discord is not recognized or valid. Here are a few steps you can take to troubleshoot and resolve the issue:

1. Check Webhook URL: Double-check the webhook URL you've provided in your GitHub repository settings. Make sure it's correctly copied and pasted from Discord without any extra spaces or characters.

2. Recreate Webhook: In some cases, recreating the webhook on Discord can solve the issue. Delete the existing webhook in your Discord server and create a new one. Then update the webhook URL in your GitHub repository settings.

3. Check Permissions: Ensure that the webhook has the necessary permissions in your Discord server. The webhook needs the "Manage Webhooks" permission in the channel where you want it to post messages.

4. Verify GitHub Payload: GitHub sends a payload to the webhook URL whenever an event occurs. Make sure your webhook listener is configured to correctly handle this payload.

5. Check Firewall and Network Settings: Sometimes, network or firewall settings can block the communication between GitHub and Discord. Ensure that your network settings are not preventing the webhook from reaching Discord's servers.

6. Use HTTPS: Ensure that both the GitHub webhook URL and the Discord webhook URL use the HTTPS protocol. Discord requires secure connections for webhooks.

7. Test with Another Service: You can also try setting up a test webhook to a service other than Discord to see if the issue is specific to Discord or if there might be a problem with GitHub's webhook functionality.

8. GitHub Status: While it's less likely, there could be a temporary issue on GitHub's end that's affecting webhook functionality. You can check GitHub's status page or their official support channels for any known issues.

[meumairakram]

I am also having some issues with the webhook's delivery. It was all working great till the last month and gets triggered in a few seconds after the push, and now even after 15 minutes some times, its not sent. There is nothing in the deliveries log about it too.
Unless I redeliver an existing delivery, then it would also trigger that pending webhook.

[Yash-Dobariya]

Check Delivery Logs: Continue to monitor your webhook delivery logs for any patterns or errors that might shed light on why some deliveries are delayed.

GitHub Status: Although less likely, it's worth checking GitHub's status page for any known issues with webhook deliveries. Sometimes, platform-wide issues can affect webhook performance.

Webhook Destination: Ensure that the destination server or service you're using for your webhooks (e.g., Discord) is functioning correctly and isn't experiencing any delays or downtime on their end.

Webhook Payload Size: Large payloads can sometimes lead to delays in delivery. Ensure that your webhook payloads are within the size limits defined by GitHub.

GitHub Configuration: Revisit your GitHub webhook configuration to ensure that everything is set up correctly, including the events you're subscribed to and the payload format you expect.

Rate Limiting: Review both GitHub and Discord's rate limiting policies to ensure you're not hitting any rate limits that could delay deliveries.

Retry Logic: Consider implementing a retry mechanism in your webhook listener to handle cases where a delivery isn't received promptly. This can help ensure that critical data is not missed.

[Infer2]

hey @Thunderrock424242 Here are the steps to create a webhook for GitHub and Discord:
Open your Server Settings and head into the Integrations tab.
Click the “Create Webhook” button to create a new webhook.
You can edit the avatar and name of the webhook, and choose what channel the webhook posts to.
Copy the webhook URL and append ‘/github’ at the end of it. This will make sure the webhook displays GitHub messages properly.
Open the webhook settings in your GitHub repository settings (Settings > Webhooks).
Click the “Add webhook” button, and enter the Discord-generated URL in the “Payload URL” section.
For content type, stick with application/json, then customize which kind of events trigger webhook messages.
Click the last “Add webhook” button beneath the event notifications customization option, and you’re all set!
Hope you'll find this helpful.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[daniel-molina23]

Hello, getting a 400 response with body in the response saying {"message": "Cannot send an empty message", "code": 50006}
I followed the instructions of putting wehook link in Payload URL, then using application/json as Content-Type, and finally only using push events, and it wasn't working. This failed for both the initial ping and the git push with some comment in the commit, which didn't make sense. In the payload of the request payload I have {"head_commit": {"message": "Update README.md" }} which is my commit message, as well as {"commits": [{"message": "Update README.md"}]}. Keep in mind these small JSON payloads have much more information but it was the only place where the message error was applicable. Hope you can help me. I have also tried to delete webhook and retry with new one, but nothing.

[daniel-molina23]

NVM, all you gotta do is

1. delete hook

2. create new hook

3. add /github at the end,

4. select content type to `application/json`

taken from this thread.