-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uploading cartridges code to staging environment using the SFCC-CI client #474
Comments
any news on that bug? We have tried with node v14.16.1 and have regenerated the certificate without success. |
I have subscribed to this issue because I am experiencing the exact same behavior, with the one difference that I was able to deploy the code the first time without any troubles, but trying it a second time has given me the errors @gmoulin mentioned. I have tried the same steps mentioned in the bug and still receiving the same error.
|
Did anyone figured out the issue and any solutions to fix it? |
It seems we are facing the same issue here. Following for potential fix. |
Facing the same issue with error : |
sfcc-ci Version
2.11.0
NodeJS Version
14.17.5
sfcc-ci Path
/cygdrive/c/Users/g.moulin/AppData/Roaming/npm/sfcc-ci
Host OS Details
Windows
Microsoft Windows 11 Pro
10.0.22000 N/A Build 22000
Description
Hello,
I am currently using Eclipse and UX studio to upload code to a staging instance and I want to replace this setup with the SFCC-CI client.
I managed to install the tool using the documentation on https://github.com/SalesforceCommerceCloud/sfcc-ci .
I set up an account.demandware.com API key for it.
I set up my staging instance according to the documentation. ("Open Commerce API Settings" and "WebDAV Client Application Permissions")
I configured the dw.json file like this: (passwords and email redacted)
{
"client-id": "becf4f98-93d9-48fd-aa2f-d5d32953562b",
"client-secret": "xxxxxxxxxxxxxx",
"username": "[email protected]",
"password": "xxxxxxxxxxxxxx",
"hostname": "staging-eshop-xxxxx.demandware.net"
}
I manage to get the authentication and basic commands working.
But when I tried to upload code using the "sfcc-ci code:deploy" command, it does not work.
I tried:
sfcc-ci code:deploy test.zip -i www-staging.xxxxx.com
Got a "403 Forbidden" error.
sfcc-ci code:deploy test.zip -i staging-eshop-xxxxx.demandware.net -c /path/to/cert/cert.p12 -p "cert passphrase" -D
(redacted)
Got Error code: EPROTO, message: write EPROTO 19628:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:c:\ws\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1544:SSL alert number 40
, stack: Error: write EPROTO 19628:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:c:\ws\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1544:SSL alert number 40
Checking the debug, I saw the "Assuming staging-eshop-xxxxx.demandware.net is a staging instance, replacing with cert.* format" sentence, so I tried
sfcc-ci code:deploy test.zip -i cert.staging.eshop.xxxxx.demandware.net -c /path/to/cert/cert.p12 -p "cert passphrase" -D
Got the same error.
Please note that I can upload code using Eclipse and I have access to the staging environment WebDav using WinSCP without problems.
From my research, it seems the error is linked to the TLS version, but I did not find any solution to force it. (Already tried forcing the TLS version for node, without success)
Relevant log output
The text was updated successfully, but these errors were encountered: