Error: self signed certificate
See original GitHub issueError with self signed certificate
----------------------------------------------------------------
--------------- 🔥🔥🔥 A error occurred 🔥🔥🔥 --------------
----------------------------------------------------------------
----------------------------------------------------------------
---------------------- Full Error below ----------------------
Error: self signed certificate
at TLSSocket.onConnectSecure (_tls_wrap.js:1321:34)
at TLSSocket.emit (events.js:210:5)
at TLSSocket._finishInit (_tls_wrap.js:794:8)
at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:608:12) {
code: 'DEPTH_ZERO_SELF_SIGNED_CERT'
}
Error: Error: self signed certificate
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:9
Top Results From Across the Web
nodejs - error self signed certificate in certificate chain
I am getting error while using SelfSigned cert for ftp on windows and using ftp npm module. Is the solution different for it...
Read more >6 Ways to fix : SSL certificate problem: self signed ... - Jhooq
Scenario 1 : Git clone - SSL certificate problem: self signed certificate in certificate chain. It is one of the most common scenario...
Read more >I get "Certificate is not trusted because it is self-signed" error ...
There might be several possible reasons why you get this error when you try to access your web site: A self-signed certificate was...
Read more >Understanding Self-Signed Certificate in Chain Issues on ...
It means that the certificate attached to the package is a way to be sure that the package was not modified from the...
Read more >A Simple Explanation of SSL Certificate Errors & How to Fix ...
Certificates issued by the server are often referred to as self-signed certificates. SSL certificate not trusted error in firefox.
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
This is probably related to the following pull request: https://github.com/SamKirkland/ftp-deploy/pull/5
The fastest workaround is to use, paradoxically,
security: strict
(I just successfully tested it). Be sure to specify the action version so it doesn’t break your pipeline again when/if this gets fixed.Same here, we’ve set
security: loose
expecting that to resolve it but it doesn’t help. All our servers are self-signed and it’s not something we can change frustratingly