---
title: "Discussion on \"\"Unable to verify the first certificate\": when Node's --use-system-ca hint won't help\"\" | Hashnode"
description: "Discussion on \"\"Unable to verify the first certificate\": when Node's --use-system-ca hint won't help\"\". TL;DR. Node's \"unable to verify the first certificate\" error now ends with a hint to try --use-system-ca. The flag helps when a root CA is missing and installed in the system store. It cannot help whe"
url: "https://hashnode.com/posts/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help/6aeb659d9498c6c028589f33"
---

[Feed](https://hashnode.com/feed) /

Discussion

# ["Unable to verify the first certificate": when Node's --use-system-ca hint won't help"](https://uptimepage.hashnode.dev/unable-to-verify-the-first-certificate-when-node-s-use-system-ca-hint-won-t-help?utm_source=hashnode&utm_medium=feed)

TL;DR. Node's "unable to verify the first certificate" error now ends with a hint to try --use-system-ca. The flag helps when a root CA is missing and installed in the system store. It cannot help whe

Nov 4 · 7 min read · uptimepage.hashnode.dev  
Read the article

-   [#node](https://hashnode.com/tag/node)
-   [#security](https://hashnode.com/tag/security)
-   [#devops](https://hashnode.com/tag/devops)
-   [#debugging](https://hashnode.com/tag/debugging)

## Written by

[Artem Senenko](https://hashnode.com/@slima4)

@slima4 · Cyprus

  
[View profile](https://hashnode.com/@slima4)

uptimepage

Software engineer with 20+ years building and running production systems: microservice architecture on Kubernetes, cloud infrastructure on AWS and Terraform, and security-critical SaaS in the fintech domain.

## Responses 1

Markdown supported · ⌘↵ to post

[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.
