CLI troubleshooting

Self-signed certificate in certificate chain error

When working with eWizard CLI, you might encounter the following error:

ERROR: self-signed certificate in certificate chain

This error typically indicates that an attempt is being made to establish an HTTPS connection with a server that uses either:

• A self-signed SSL certificate

• A certificate signed by an untrusted certification authority (CA)

However, since this issue affects only individual users rather than all users, the problem is likely localized to specific users' systems or networks rather than the server itself.

Probable causes:

1. Corporate firewall or proxy

   • Corporate firewalls or proxies might intercept traffic and replace original certificates with the custom ones. These certificates, however, are not trusted by Node.js.

2. Antivirus software

   • Some antivirus programs replace certificates with their own, causing trust issues.

3. Manually installed certificates

   • Users can install own self-signed certificates, which aren't inherently trusted by Node.js.

Suggested solutions

Here are steps to resolve this issue:

1. Add corporate or custom certificate to Node.js.

   If you're using a corporate or custom certificate, add it to Node.js's list of trusted certificates.

   • Confirm the issue is resolved by running the failing eWizard CLI command again.

2. Try logging in or running the CLI command without corporate firewalls, proxies, or antivirus software to identify if one of these is causing the issue.

3. Test with a different device or network.

   If the error persists, try to reproduce the issue on a different device or in a different network environment. This can help isolate whether the problem is related to a specific system or network.