I created a general app, and configured the webhooks to receive notifications (meeting started, user joined, etc), but I am not receiving any notifications on the webhook url. I have checked the URL and it is working (I can send POST requests via postman, curl, etc). Bu when I start the Zoom meeting, no notification is being sent to the webhook url. I have checked all the settings, and it all seem to be correctly setup. Did something change recently? I had a previous app, similar, in development, and it used to work. However, I deleted and started a new app, and it’s no longer working, same webhook url.
1 Like
Hi @chuks
Thanks for reaching out to us!
Nothing has changed on our end recently. Can you please make sure to save the changes you make to your subscriptions and to authorize the app
Hi @elisa.zoom thanks for your response. Yes, I’ve saved the changes and authorized the app, but it still doesn’t send any webhooks. I’m testing in development (not production) and no hooks come through the url endpoint. I’ve also tested that the url endpoint works (I can do a curl/postman POST) and it responds as expected, but not when I trigger meeting start, meeting end, participant join, etc…
Interestingly, used to work just fine until two weeks ago (same url endpoint for webhooks on my backend), so I started suspecting perhaps something happens at the 1yr mark (it’s been a year since setting up the development app), but couldn’t find any documentation on that anywhere. Unclear how else to debug.
Hi @chuks
Thanks for sharing more details about this.
I can take a closer look to this. I will send you a DM please follow up accordingly
I think I’ve boiled down this issue. It seems Zoom blacklisted my domain name, or at least my domain name is not whitelisted. Anyone having this same issue? I can validate other urls for the webhook, but as soon as I enter my url, it does not validate. Why would this happen?
1 Like
Hi @chuks
would you mind sharing the solution to this issue? we have another developer facing this @Axya
Oh, the issue was from my DNS security settings on Cloudflare, which was blocking traffic from Zoom. There’s probably something with Zoom’s headers that Cloudflare security didn’t like. when I disabled all of the highest security on DNS, it started allowing traffic in. This was the reason why I could hit the endpoint using Postman and not from zoom. I’m not exactly sure what Cloudflare didn’t like about Zoom’s headers, but it was just easier for me to turn it off to get it to work and I am ok with that for now.
No worries @elisa.zoom ! Honestly, I sometimes wish I can do some work for zoom, because of all the issues I’m seeing. I’m still building and am seeing several improvement areas especially on your Linux SDK. The latest SDK seem to have regressed as it was compiled with older C++ binaries. Honestly, I wish there was a way to create a native GoLang or Python or some other high level programming language SDK. It’s insanely difficult to follow up as things break from one release to another. C++ is definitely a hair pull!
1 Like