Hello. We've gone through all the steps listed on the various KB articles.
However after creating the cert and export password for that cert, when we use the domain cert.staging.na01.YYY.demandware.net., the deploy step always fails with this error
Error: Network or certificate error
Error: An error occured. Try running the command again with -D,--debug flag.
[DEBUG] Error code: EPROTO, message: write EPROTO 70000:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:c:\pkg-fetch\precompile\node\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1544:SSL alert number 40
, stack: Error: write EPROTO 70000:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:c:\pkg-fetch\precompile\node\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1544:SSL alert number 40
at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)
I am using the latest version on sfcc-ci on Windows. It's not working in Jenkins either. (We've done the client:auth step just fine).
SFCC support had us recreate the cert where the "Common Name (e.g. server FQDN or YOUR name)" matched the hostname and even that did not work.
This points to a TLS 1.1 v/s 1.2 issue but we dont quite know how to resolve it?
Hello. We've gone through all the steps listed on the various KB articles.
However after creating the cert and export password for that cert, when we use the domain cert.staging.na01.YYY.demandware.net., the deploy step always fails with this error
Error: Network or certificate error Error: An error occured. Try running the command again with -D,--debug flag. [DEBUG] Error code: EPROTO, message: write EPROTO 70000:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:c:\pkg-fetch\precompile\node\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1544:SSL alert number 40 , stack: Error: write EPROTO 70000:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:c:\pkg-fetch\precompile\node\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1544:SSL alert number 40
I am using the latest version on sfcc-ci on Windows. It's not working in Jenkins either. (We've done the client:auth step just fine).
SFCC support had us recreate the cert where the "Common Name (e.g. server FQDN or YOUR name)" matched the hostname and even that did not work.
This points to a TLS 1.1 v/s 1.2 issue but we dont quite know how to resolve it?