Vernemq 1.12 Webhooks Lets Encrypt certificate issue

[djsakisd]

Hi @ioolkos

After updating to latest version 1.12 we experience issue with webhooks authentication since they do not work anymore. All of our webhooks are using https with le certificate (CLIENT ALERT: Fatal - Unknown CA).

After further investigation it seems to be affected by an issue with Erlang and LE certificates , more info here : https://blog.voltone.net/post/29

1.11 and below are working fine with webhooks. OS: Ubuntu 20.04.3 LTS

[ioolkos]

@djsakisd thanks for bringing this to attention. What Erlang version did you use to compile Verne?

---

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq :point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

[djsakisd]

@ioolkos you're welcome , happy to help.

I tested with precompiled binaries, haven't compiled yet.

[ioolkos]

Ah, last binary was built before using a patched Erlang version. Need to do that then.

Okay, so this affects Erlang TLS clients when the other end (server) is using Letsencrypt certs. For Verne this is the Webhook plugin, as it is the client.

cc @varnerac fyi

---

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq :point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

[varnerac]

I’ll take a look in next few days. Thanks.

[ioolkos]

@varnerac it's just something to be aware of, regarding the Erlang version used. See: https://blog.voltone.net/post/30, regarding Hackney. I don't think we actually have to do anything in addition.

---

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq :point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.