301 or 302 Redirection error for Webhooks URL

Modified on: Tue, 22 Jun, 2021 at 12:33 AM

Scope

A webhook that returned "success", but it is not functioning properly. 

Failure reason: Received error code 302 from the server. Redirection is not supported in webhooks.

Failure reason: Received error code 301 from the server. Redirection is not supported in webhooks.


The webhook throws 3XX status code because redirection is not supported in webhooks. This means that the URL that you have configured in your webhook is calling another URL in return which is not supported due to security reasons. Simply put, the webhook URL that you have configured should return the status instead of the redirected URL.

Solution

 

Please note that Chargebee does not support a redirect URL and you would need to configure the URL of your actual Webhook listener server in the Webhook URL field. This is the reason why the webhook is failing.


You can change the webhook URL without redirection. Navigate to Configure>Webhooks>Test webhooks to test your webhook


The automatic retries from Chargebee will happen only for 200 errors, with respect to the 300 errors, these have to be retriggered manually.
M
Monica is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.
×