Skip to main content

What does 'Webhook call failed' mean and how can it be fixed?"

What does the message mean?​

A "Webhook call failed" means that Wallee attempted to send a notification (webhook) to a configured URL, but the call was unsuccessful. Webhooks are used to inform your server about important events, such as a successful payment or a status change. The error message appears in your Space under manual-tasks.md.

Why does this message appear?​

Possible reasons could be:

  1. Server not reachable

    If your server is not reachable, Wallee cannot successfully deliver the webhook. This can be caused by server outages, maintenance work, or network issues. :arrow-right: Check if your server is online and responding to requests. Test the webhook URL directly in a browser to ensure it is accessible.

  2. Incorrectly Configured Webhook URL
    Only one webhook URL can be set per space. If multiple URLs have been entered or changes have been made, this can lead to confusion or faulty webhook calls. :arrow-right-long: Click here and make sure that only one correct URL is saved. Remove any unnecessary entries and verify that the URL has been entered correctly. Here you will find a guide on how to reset Webhook URL and Listeners completely: How to reset Webhooks

  3. Webhook is blocked by a firewall or security plugin

    Firewalls or security plugins may sometimes block webhook requests from Wallee. This often happens when unknown IP addresses are classified as potential threats. :arrow-right: Check your firewall and security settings, and add Wallee’s public IP addresses to the whitelist. If you're unsure how to do this, contact your hosting provider or system administrator.

Whitelist the following IP addresses:

52.211.247.160  
52.211.171.77  
52.211.239.229  
52.211.209.173  
52.208.210.84  
52.212.109.85  
52.210.89.1  
52.212.185.152  
52.212.192.130

  1. Incorrect Server Response (HTTP Error Messages)

    An HTTP error code such as 400 (Bad Request), 403 (Forbidden), or 500 (Internal Server Error) indicates that the server is either rejecting the request or unable to process it internally. :arrow-right: Check the server logs to determine why the request is failing, and resolve the underlying issue.

Deactivation of Webhook Listener​

After 13 consecutive failed webhook deliveries, Wallee automatically disables the webhook listener to prevent further errors. This means that no additional webhooks will be sent until the listener is manually reactivated.

Please check the status on your webhook listener here. You can manually activate it again.