Adding a Dedicated CA File to Verify a Node SSL Certificate
When trying to add a node with signed SSL certificates to Shares, selecting the
Verify SSL Certificate option may result in a failure to
add the node if the node's SSL certificate is not recognized by the Certifcate
Authority (CA). Shares displays the following error message at the top of the page
when you try to add the node: "Status: Not pingable. Internal error.
(Error-35)". You can resolve this error in one of two ways:
- If the node is using the default self-signed SSL certificate provided by Aspera, the certificate is not recognized by any CA. You must clear Verify SSL Certificate option.
- If the node is using a signed SSL certificate, you must add to Shares a dedicated CA that recognizes the certificate.