Description

After PR #684 , the HTTP integration still fails when using server certificates signed by a custom CA.

ChirpStack v4.14.0.

CA mounted in /etc/ssl/certs.

External tools (openssl, curl) validate the cert correctly with the CA.

Expected behavior

HTTP POSTs should succeed when the custom CA is trusted by the system or explicitly configured.

Actual behavior
Requests fail. Using a public CA works fine.

Steps to reproduce

Run ChirpStack container.

Mount custom CA in /etc/ssl/certs.

Configure HTTP integration with an HTTPS endpoint signed by this CA.

Trigger an uplink → request fails.

Notes

The HTTP integration currently provides no option to supply a ca_cert, unlike other integrations.