One month down in 2025: How are your resolutions coming along? Check out how to get back on track here.
Forum Discussion
Webhook Returning Empty Response Error
I have 3 apps that are configured identically. 2 Development and 1 production.
Each has a webhook URL specified. The live production one keeps erroring out with the below error. I can immediately r...
Greg-DB
Dropbox Staff
Dropbox StaffThanks for the report. If/when a webhook URI is automatically disabled, we do send an email notifying you of that. Please make sure that the email address on the account that owns the app is up to date and can receive email from the official Dropbox email domains.
It sounds like this the webhooks functionality is working for you now, so it may have been a transient network disruption. If you see this again though, please open an API ticket with the relevant app key(s) and webhook URI(s) so we can investigate this specifically. Thanks!
Hi Greg,
Thanks for the quick response. I did update my email earlier, although it was previously using a google email, and it wasn't coming into spam or trash. That's good to know though, hopefully, I will get an email if it comes up again. I will review what you linked.
On the webhook issue, it was doing this for the last 24 hours. My attempts to fix included removing and re-adding. It only started working when I added it twice, waited 10 minutes, and then removed the errored one. It's very odd. No problems since. That does not fit the profile of a network issue.
Thanks again!
Derek
Hi Greg,
This indeed did happen again, and I indeed did NOT get an email. We checked all the logs. We are using G-Suite, and no email was ever sent. As such, functionality was broken for a long period before we realized it.
1) The email system for Webhooks is not working or reliable. I'm not sure what to do??
2) Why are you disabling after a failure, why not automatically re-enable. It's not clear what the original issue was if it occured from the DB side as we have no events that line up with the issue. Regardless, problems occur, and so to shutoff webhooks for an entire app and all its users look like a poor choice; why not re-enable automatically with exponential backoff.
Here is the latest error we got, all we had to do was disable, and re-enable, which could have been done programmatically by DB:
Error: Internal Dropbox error
Request:
POST <redacted>Response:
HTTP/1.1 N/A UnknownResponse Body (First 256 bytes):
(No response body)Thank you for your help Greg-DB
- Greg-DB
Thanks for following up. In that case, please do please open an API ticket with the relevant app key(s) and webhook URI(s) so we can investigate this failure for you. We can also check our logs for see what happened with the email. Please make sure to open the ticket while signed in to the account that owns the app in question.
And thanks for the feedback regarding the disabling behavior. I can't speak to why the system was originally designed in this way, but I'll pass this feedback along to the team.
About Discuss Dropbox Developer & API
Make connections with other developers
