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.
To start configuring your webhook, see this article and check our documentation for more information. You can also check the example codes we provided.
Remember to verify your request.
To start configuring your webhook, see this article and check our documentation for more information. You can also check the example codes we provided.
Remember to verify your request.
Response does not match challenge.
-
The webhook server is working, but the challenge is either not returned from your server or is different from the one provided by ChatBot.
-
Ensure that you return the exact same challenge via your server.
Request failed with code “CODE” (“CODE MESSAGE”)
-
The provided URL returns an error.
-
Make sure that your server returns a
200 OKstatus to make it work. In most cases, it’s caused by the incorrect webhook code configuration.
The maximum number of redirects has been exceeded
-
The provided URL returns more than one redirect.
-
Make sure that your server doesn’t return a redirect loop.
The maximum time limit of 10s has been exceeded
-
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.
Unsupported SSL/TLS version
-
The provided URL returns an expired/private/unsupported SSL certificate.
-
The URL should be available on a publicly valid certificate.
Exceeded the download limit of 100kb/ maxContentLength size of 102400 exceeded
-
The response from the provided URL is too big.
-
Your server is probably returning something more than a challenge (e.g. whole site HTML).
The URL is unreachable
-
The provided URL doesn’t exist or isn’t publicly accessible (e.g. localhost).
-
Ensure your server is up and running, and the URL is public.
The JSON response cannot be parsed. This might be because it’s actually not JSON.
-
Make sure your webhook’s code has all elements from the PHP code example provided in our documentation.
Request failed with code 404 (Not found).
-
If your webhooks triggers the Failure block, check the connection. Go to the Integrations panel and reconnect the connection with the provided button.
-
If the webhooks fails after the reconnection, check if your server is running.
Error 500
-
There is a problem with your server. Check the server and its logs.
-
Ensure the connection works and the server is available.
Error 403
-
Either the request tokens are missing or invalid, or the credentials associated with the tokens don’t have access to the specified resource.
-
Ensure your request is correctly verified.
Error 502
-
This error indicates that the server is listening but can’t forward the request to the service. It usually occurs when the service is not running, running on a different port, or simply crashing.
-
Check the provided URL and token.
Something went wrong
-
There’s a problem with the webhooks feature on our end. Please try again later and contact us if the issue persists.
Read more:
