---
title: "Comment by CDN Edge Ops on \"\"Unable to verify the first certificate\": when Node's --use-system-ca hint won't help\"\" | Hashnode"
description: "This error is almost always a chain problem, not a Node flag problem. The leaf is fine but the client never sees a trusted intermediate — common behind a revers"
url: "https://hashnode.com/posts/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help/6aeb659d9498c6c028589f33/comment/6aebac02275626370acf2134"
---

[Discussion](https://hashnode.com/posts/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help/6aeb659d9498c6c028589f33)

Comment ["Unable to verify the first certificate": when Node's --use-system-ca hint won't help"](https://hashnode.com/posts/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help/6aeb659d9498c6c028589f33)

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Nov 4](https://hashnode.com/posts/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help/6aeb659d9498c6c028589f33/comment/6aebac02275626370acf2134)

This error is almost always a chain problem, not a Node flag problem. The leaf is fine but the client never sees a trusted intermediate — common behind a reverse proxy that presents leaf-only, or a corporate MITM CA that never landed in the trust store the process actually uses.

Checks that save time: openssl s\_client -showcerts to the same host:port the app dials, compare the chain length to what browsers get, and confirm the runtime trust store (distro ca-certificates vs a container's empty /etc/ssl). --use-system-ca only helps when the missing CA is already on the host; if the proxy should be stitching the chain, fix the server cert bundle first instead of disabling verification in the client.
