OpenSSL certificate verify failed when trying to connect to ci.appveyor.com
Our build is driven from a rake (Ruby make) script, so I'm trying to add a rake task to upload our test results to the test results endpoint as described here.
This task is hitting an error with certificate verification, and I've used this script to diagnose the problem.
The output of the script is shown below. Please can you help us resolve this issue?
C:/Ruby193/bin/ruby (1.9.3-p551)
OpenSSL 1.0.0o 15 Oct 2014: C:/Users/Luis/Code/luislavena/knap-build/var/knapsack/software/x86-windows/openssl/1.0.0o/ssl
SSL_CERT_DIR=""
SSL_CERT_FILE=""
HEAD https://ci.appveyor.com:443
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
The server presented a certificate that could not be verified:
subject: /C=US/O=GeoTrust Inc./CN=RapidSSL SHA256 CA - G3
issuer: /C=US/O=GeoTrust Inc./CN=GeoTrust Global CA
error code 20: unable to get local issuer certificate
Possible causes:
`C:/Users/Luis/Code/luislavena/knap-build/var/knapsack/software/x86-windows/openssl/1.0.0o/ssl/cert.pem' does not exist
`C:/Users/Luis/Code/luislavena/knap-build/var/knapsack/software/x86-windows/openssl/1.0.0o/ssl/certs/' is empty
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Mike Dillamore on 22 May, 2015 11:26 AM
Update: looks like the invalid certificate can be ignored using verify_mode = OpenSSL::SSL::VERIFY_NONE. That should allow us to get going.
Support Staff 2 Posted by Feodor Fitsner on 22 May, 2015 01:52 PM
Yeah, but why that certificate is considered as invalid? It's a valid RapidSSL certificate working well in any browser.
- Feodor
3 Posted by Mike Dillamore on 26 May, 2015 03:34 PM
I think we're hitting the issue reported here.
In short, it seems to be specific to https with Ruby and I think it could be fixed by adding additional certs to the Ruby installation. It's not causing us a problem however, so not a priority.
Mike Dillamore closed this discussion on 21 Dec, 2015 01:15 PM.