Troubleshoot webhook endpoint issues

Chris Aylott
Chris Aylott

Problem Symptoms

In the webhook logs or via email you receive the following message: Failed to connect to the webhook endpoint

 

Description

We wait 10 seconds for the host to respond, there are a few reasons why the webhook endpoint might be having issues.

  • IP blocked
  • Network delays  or packet loss in the route
  • Host CPU congestions

 

Resolution

You can test for packet loss / latency via traceroute or MTR to the IP of the host you entered as your webhook endpoint.

sudo mtr X.76.21.9 --report
Start: 2022-05-25T16:15:08+0200
HOST: ip-192-168-0-246.ec2.intern Loss%   Snt   Last   Avg  Best  Wrst StDev
1.|-- ip-192-168-0-1.ec2.intern  0.0%    10    1.4 190.8   1.2 1010. 385.9
2.|-- ip-192-168-2-254.ec2.inte  0.0%    10    2.2 275.9   1.5 973.5 437.0
3.|-- 195-190-228-188.fixed.kpn  0.0%    10   16.0 262.1  12.3 917.3 401.2
4.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0.  <<<<<<< Note the packet loss

 

Resources

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.