The fireblocks is not calling webhook api exposed in backend app.
Hi @rajesh-bridge-port it appears that our systems’ attempts at posting the webhooks to the URL have been timing out - “error: timeout of 15000ms exceeded”
Can you confirm that the URLs you configured are reachable?
You might need to whitelist the webhook IPs shared here
@Wilfred , Thank you for the reply
Yes , the given url for webhook is reachable and IP address are also updated in ec2-securityGroup. Please review the screenshot attached for more details
Thanks!,
Rajesh
Hi @rajesh-bridge-port could you please elaborate on what the screenshot shows?
Have you tried initiating a transaction and have not received any webhooks?
Please share the txid.
Thank you
Hi @Wilfred,
Yes, I initiated transaction and its worked fine but further process from fireblocks to customer backend is not working. Customer backend has the webhook api to write transaction data, that part is not working. Auditlog in fireblocks account also not showing any webhook logs.
This is the link Create Transaction which I follow to create the transaction. Here, step POST /webhook is not working or not calling.
This is the webhook api which exposed from customer backend : https://107.23.30.22.nip.io:8000/api/webhook - this api endpoint accessible and working fine with postman and web browser.
Txid : b460c6f0-1835-4b84-84a4-1ab01e9a06dc
Thanks,
Rajesh
Hi @rajesh-bridge-port please be aware that the Audit Log is not designed to capture any webhook logs. Please see this Help Center article to learn more about the Audit Log feature
Are you running any logging on your webhook server?
Is your webhook server responding with a 200 response?
Do you have any logs to show that “further process from fireblocks to customer backend is not working.”?
Hi @Wilfred ,
Please review the logs below, there is no request from fireblocks to customer backend app to connect webhook
I customized this GitHub - fireblocks/ncw-backend-demo: Fireblocks Non custodial wallet demo backend repo for the customer backend and deployed in ec2 instance with this address https://107.23.30.22.nip.io:8000
this is the webhook end point https://107.23.30.22.nip.io:8000/api/webhook
Hope you have experience in this repo GitHub - fireblocks/ncw-backend-demo: Fireblocks Non custodial wallet demo backend
Thanks,
Rajesh
Hi @rajesh-bridge-port can you clarify the expected behaviour here?
Please review the Developer Center article on configuring webhooks
I just checked the logs for txid b460c6f0-1835-4b84-84a4-1ab01e9a06dc
and I can see that the timeouts still persist
message:Failed to post webhook to URL https://107.23.30.22.nip.io:8000/api/webhook, error: timeout of 15000ms exceeded
Could you try running an ngrok server or use a site such as https://webhook.site/ for testing?
Hi @Wilfred ,
This address [https://107.23.30.22.nip.io:8000] is accessible from outside and all ip address which are mentioned in the (Configure Webhooks) page also enabled in ec2 security group. What is the issue with fireblocks? Will fireblocks not support this type of domain address?
Please try it through web bowser, you can confirm that its working
Please provide us with precise solution to process further
Thanks,
Rajesh
Hi @rajesh-bridge-port what about https://107.23.30.22.nip.io:8000/api/webhook?
Is the webhook server responding with any response?
This is what I am seeing at the moment
Hi @Wilfred ,
Yes, this is correct. It will not allow GET method. This webhook api is work with POST request method.
So, the webhook api is reachable , right? please confirm.
Thanks,
Rajesh