Don't receive any events from Webhook
See original GitHub issueBug Report
Current Behavior
Receive ERROR probot: Not Found Error: Not Found at Request.callback (./node_modules/superagent/lib/node/index.js:706:15) at IncomingMessage.parser (./node_modules/superagent/lib/node/index.js:916:18) at IncomingMessage.emit (events.js:187:15) at IncomingMessage.EventEmitter.emit (domain.js:442:20) at endReadableNT (_stream_readable.js:1081:12) at process._tickCallback (internal/process/next_tick.js:63:19)
when trying to receive context of event from Webhook.
// Your code here
module.exports = app => {
app.on('issues.opened', async context => {
const params = context.issue({
body: 'Hello World!'
});
await context.github.issues.createComment(params);
});
};
Expected behavior/code Should see that comment appears when new issue was opened.
Environment
- Probot version(s): latest
- Node/npm version: Node 10.4.1/npm 6.1.0
- OS: OSX 10.13.4
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Complete Guide to Troubleshooting and Debugging Webhooks
Webhook URL, Event triggers are sent as an HTTP request to a given endpoint; ... You don't want to be getting webhook requests...
Read more >Not receiving webhook event in my application
Hi, I want to build a conversational chat bot using java for twitter. I had successfully make the webhook URL to receive the...
Read more >Receiving Events via a Webhook - RingCentral Developers
By default, endpoints will not receive any events, as they are subscribed to none. To know more about the subscription process, see Creating ......
Read more >Best practices for using webhooks | Stripe Documentation
Your webhook endpoints should be configured to receive only the types of events required by your integration. Listening for extra events (or all...
Read more >Missing events and no "sync_error" recieved on that webhook ...
Are there a risk that we don't always receive “sync_error” for a project when something happens or what could be the issue of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I solved my issue. I was running another process on port 3000. Once I killed that process and restarted my probot app everything worked fine. @laisti you might want to see if you have another process running on port 3000 (or whatever port your probot app is running on). I was seeing the exact same error/stacktrace as the one you reported.
I’m currently experiencing this issue as well. No other processes running on a conflicting port.