Webhooks — Troubleshooting
Related setup guideSetting up Webhooks? See the Webhooks integration setup guide.
| Error message | Likely meaning (TL;DR) | Recommended next steps |
|---|---|---|
| Error with create callback | Confirm the webhook or callback URL is correct and publicly reachable. Make sure the account used has permission to create webhooks. Reconnect the integration and try again. | |
| Error with create callback: Site Disabled | The service hosting the webhook URL responded that the target site or account is disabled — for example a suspended or expired account, a deactivated app, or hosting that was shut down — so the webhook could not be created. | Check that the platform hosting the webhook endpoint is active and the account/site is not suspended. Once it is restored (or with a new endpoint URL), update the webhook URL in the integration settings and reconnect the integration. |
| Error with close callback | Xyte tried to send the close incident webhook/callback, but the external endpoint failed or did not respond successfully. | Confirm the close incident URL is correct and publicly reachable. Check that the target system accepts the close callback payload. Reconnect the integration and try again. |
| Error using Create URL : hostname "abcd.com" does not match the server certificate | The webhook URL does not match the security certificate. Contact support. | |
| Webhook URL is not updated | ||
| Error with create/update/close callback: Not Found | The receiving server answered 404: the webhook URL or path is wrong, or the endpoint was removed. | Check the Create, Update and Close URLs in the integration against the receiving system, update them, and use Test to confirm. |
| Error with create/update/close callback: Unable to connect to webhook · Failed to open TCP connection to … (Connection refused) | The receiving server could not be reached: it is down, the address is wrong, or a firewall blocks the connection. | Confirm the endpoint is up and publicly reachable over HTTPS, and that its firewall allows incoming requests. Then use Test. |
| Error with create/update/close callback: Too Many Requests | The receiving server is rate-limiting the webhook calls. | Ask the receiving system's admin to raise or remove the rate limit for these calls. Calls succeed again once the limit clears. |
| Error with create/update/close callback: Bad Request | The receiving server rejected the request body or headers. | Compare the payload template and headers with what the receiving system expects (required fields, content type, authorization header), fix them, and use Test. |
| Error with create/update/close callback: Payment Required | The receiving service answered 402: its account or plan needs payment or an upgrade. | Ask the owner of the receiving service to check its billing or plan, then use Test. |
Updated 6 days ago
What’s Next
Did this page help you?