Learn how to resolve the most common issues in ChatBot.
During the configuration process, you may encounter some problems with adding webhooks to your ChatBot account. The most popular errors and their possible origins are listed below.
The webhook server is working, but the challenge is either not returned from your server or isn’t the same as the one provided by ChatBot. Make sure that you return the exact same challenge via your server. You can read more about the verification process in this article.
The provided URL returns an error. Make sure that your server returns a
200 OK status to make it work. In most cases, it’s caused by the incorrect webhook code configuration. You can use our ready-to-use code examples for debug purposes.
The provided URL returns more than one redirect. Make sure that your server doesn’t return a redirect loop.
The provided URL hasn’t returned any data in the 10 second period. Requests will be automatically rejected after the 10 second timeout. It’s not possible to increase/decrease this timeout.
The provided URL returns an expired/private/unsupported SSL certificate. The URL should be available on a public valid certificate.
The response from the provided URL is too big. Your server is probably returning something more than just a challenge (e.g. whole site HTML).
The provided URL doesn’t exist or isn’t publicly accessible (e.g. localhost). Make sure that your server is up and running, and the URL is public.
There’s a problem with the webhooks feature on our end. Please try again later, and contact us if the issue persists.