-
Notifications
You must be signed in to change notification settings - Fork 224
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
us.blockchain.ibm.com.cert failing to validate #78
Comments
Are you using hfc npm module? if yes, what version are you using? If you have enabled |
yes. "hfc": "0.6.5", |
I found this line. It's in github. Should it be removed or set to false? |
I tried both, but no change. I tried commenting out -ECDSA- in the list of suites and got bad handshake. |
the membership services eca and tca certs have expired |
@belltanellc can you give us your network ID? we can refresh those certs |
Sorry. Was in a meeting. |
@belltanellc the network ID should be on your dashboard on top left. it should be a long string. |
f6efed9eb5ec4025996d39ad4889bd0e |
It's been running fine in Bluemix for months. Now it will not start and errors on
OUT chain_setup.js Deployment request: {"fcn":"init","args":["IGNORE","ME"],"chaincodePath":"chaincode/","certificatePath ":"/certs/peer/cert.pem"}
OUT msg: 'Certificate has not been signed by a trusted authority. [x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "eca")]' }
The cert shows valid issuer and expiration date. Not After : Jun 12 12:00:00 2019 GMT
The text was updated successfully, but these errors were encountered: