Support for self signed certificates
See original GitHub issueI received a support request with the following CLI failure details:
"errorType": "FetchError",
"errorMessage": "✖ Failed to authenticate\nrequest to https://index.chromatic.com/graphql failed, reason: self signed certificate in certificate chain"
The customer noted that: “There is self signed cert in yarnrc”
The yarnrc looks like:
# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# yarn lockfile v1
cafile "/path/to/certificates.crt"
lastUpdateCheck 1599849070591
strict-ssl true
NOTE: you can work around this via setting NODE_TLS_REJECT_UNAUTHORIZED=0
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
What is a Self-Signed Certificate? Advantages, Risks ...
Another strategy is to issue self-signed SSL certificates. A self-signed certificate is one that is not signed by a CA at all –...
Read more >AWS DataSync adds support for self-signed certificates
AWS DataSync now supports the use of self-signed certificates when connecting to object storage locations via HTTPS.
Read more >Adding the self-signed certificate as trusted to a browser
Adding the self-signed certificate as trusted to a browser · Open the Certificates management console, and then run the following command: certmgr. ·...
Read more >Creating a Self-Signed SSL Certificate - Heroku Dev Center
A private key and certificate signing request are required to create an SSL certificate. These can be generated with a few simple commands....
Read more >How do you get Chrome to accept a self-signed certificate?
In the address bar, right click on the red warning triangle and "Not secure" message and, from the resulting menu, select "Certificate" to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
NODE_TLS_REJECT_UNAUTHORIZED=0
is last minute fix, but, it worked for me… potentially a suggestion, but, not preferred.I guess a custom CA that uses self-signed-certs to do MITM.