Central-Webhook integration in ODK Central

[muzele]

Hello spwoodcock,
Thanks to redirect me in this discussion space.
I'm Chris.
I've just installed my ODKCentral and it's working fine.
What I need to acheive is everytime someone send a form with ODKCollect, those informations be send automatically to a API endpoint. JSON, XML, any format.
I understand that this can be acheived with central-webhook, but still struggling on how to make it work. I've followed the step describe in https://github.com/hotosm/central-webhook. But I can't have the data sent in my endpoint.
Please help !
Thanks in advance

[spwoodcock]

Hi Chris!

Could you provide some more details so I can help?

Perhaps the config you are using? The docker compose file, or dotenv settings?

Also if you have any error messages or logs, that would help too 🙏

[muzele]

env.txt
Hi spwoodcock,
I have attached my .env config file.
I don't have any error message.
Thanks

[spwoodcock]

Thanks!

Looks like you are using the webhook.site service. Does this need any form of authentication on the endpoints, or is it fully open?

Could you provide some logs or something from the central-webhook service?

docker logs central-webhook-1 (or change to the name of your docker service)

With the info you provided its impossible for me to debug any further 😅

• Can we start with what is actually going wrong? Is the issue that webhooks.site is not receiving any data when you submit to ODK? Or perhaps you can't start the webhook service? Looks like you have configured it correctly though (based on the dotenv)

• Either I need the full details of your setup to replicate it, or some logs to inspect and help diagnose 👍

[muzele]

Hey SP,
Thanks for your support.
Webhook.site service doesn't need any kind of authentication. It's fully open for testing.
When I test with postman, I get the data on webhook.site, the problem is only with ODK.

Here are the logs.

{"time":"2025-03-07T07:43:13.142209907Z","level":"INFO","source":{"file":"main.go","line":62},"msg":"listening to odk-events channel"} {"time":"2025-03-07T07:54:43.884856561Z","level":"ERROR","source":{"file":"request.go","line":47},"msg":"failed to send HTTP request","error":"Post \"https://webhook.site/96938ef9-886e-4388-8109-894acf33fa41\": tls: failed to verify certificate: x509: certificate signed by unknown authority"} {"time":"2025-03-07T07:54:43.980065653Z","level":"ERROR","source":{"file":"request.go","line":47},"msg":"failed to send HTTP request","error":"Post \"https://webhook.site/96938ef9-886e-4388-8109-894acf33fa41\": tls: failed to verify certificate: x509: certificate signed by unknown authority"} {"time":"2025-03-07T07:54:44.18118988Z","level":"ERROR","source":{"file":"request.go","line":47},"msg":"failed to send HTTP request","error":"Post \"https://webhook.site/96938ef9-886e-4388-8109-894acf33fa41\": tls: failed to verify certificate: x509: certificate signed by unknown authority"}

If you agree, I can give you access to my ODK server (it's a test server, no confidential data inside).
Thanks again, waiting to read from you !
Regards,

[spwoodcock]

So it looks like an issue with the certificate for webhook.site, not an issue with central-webhook imo.

I checked the certs and it says they are valid from 12:00 07-03-2025 (today):

The logs above show an attempt made at 07:54:43 today - so perhaps the certificate was expired or not provision by webhook.site yet?
Could you try one more time to create a submission and post any logs you receive? Thanks 🙏

[muzele]

Hey SP,
I sent another test and I get the same error related to certs.

Thanks,

[spwoodcock]

So https://webhook.site forwards the request to a server you have running somewhere, right?

The error about using self-signed certs is likely not from webhook.site, but from the server that the request is forwarded to.
Where is the final server for the webhook hosted?
Is there a valid certificate set on the server?

There are details in webhook.site docs about configuring with self-signed certs, although I wouldn't recommend going this route: https://docs.webhook.site/cli.html#self-signed-certificates
(but you could test to confirm this is the problem, then in prod provision valid certs)