Error: self signed certificate in certificate chain

[ajaynarang]

The problem

Running Percy throws the below error
./node_modules/.bin/percy exec:start -v
[percy:config] Config file not found (0ms)
[percy:client] Creating a new build... (25ms)
[percy:core:browser] Closing browser (1546ms)
[percy:core:browser] Browser closed (1ms)
[percy:cli] Error: self signed certificate in certificate chain
at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34)
at TLSSocket.emit (events.js:314:20)
at TLSSocket._finishInit (_tls_wrap.js:937:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:711:12) (1ms)

Environment

• Node version:v12.20.1
• @percy/cli version: ^1.0.0-beta.76
• Version of Percy SDK you’re using: "@percy/cypress": "^3.1.1",
• If needed, a build or snapshot ID:
• OS version: macOS Monterey
• Type of shell command-line [interface]: zsh

Details

Running Percy throws the below issue while it over the enterprise VPN connection.
./node_modules/.bin/percy exec:start -v
[percy:config] Config file not found (0ms)
[percy:client] Creating a new build... (25ms)
[percy:core:browser] Closing browser (1546ms)
[percy:core:browser] Browser closed (1ms)
[percy:cli] Error: self signed certificate in certificate chain
at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34)
at TLSSocket.emit (events.js:314:20)
at TLSSocket._finishInit (_tls_wrap.js:937:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:711:12) (1ms)

Works ok when I disconnect the VPN.

Debug logs

If you are reporting a bug, always include logs! Give the "Debugging SDKs"
document a quick read for how to gather logs

Please do not trim or edit these logs, often times there are hints in the full
logs that help debug what is going on.

Code to reproduce issue

Given the nature of testing/environment bugs, it’s best to try and isolate the
issue in a reproducible repo. This will make it much easier for us to diagnose
and fix.

[ajaynarang]

Setting the NODE_EXTRA_CA_CERTS environment variable resolved the issue. Thanks

export NODE_EXTRA_CA_CERTS=path/to/certificate.crt

I would suggest you to please include this in your CLI documentation as well.