Skip to content
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

SSL errors on Travis #81

Closed
musoke opened this issue Sep 3, 2017 · 7 comments
Closed

SSL errors on Travis #81

musoke opened this issue Sep 3, 2017 · 7 comments

Comments

@musoke
Copy link
Contributor

musoke commented Sep 3, 2017

I'm switching a small project of mine over to trust. Builds on Travis are failing when they didn't previously. I'm getting SSL errors when testing the crate with TARGET=*-unknown-linux-* on Travis. darwin is fine, and the tests don't run on BSD or Windows. Testing locally on debian and arch linux also works.

It looks like reqwest can't find certificates:

Error { kind: Io(Error { repr: Custom(Custom { kind: Other, error: Ssl(ErrorStack([Error { code: 336134278, library: \"SSL routines\", function: \"ssl3_get_server_certificate\", reason: \"certificate verify failed\", file: \"s3_clnt.c\", line: 1264 }])) }) }), url: Some(\"https://inspirehep.net/search?of=hx&p=Higgs%3A2014aqa\")

Example log on Travis
Line where the panic happens

This looks like a related issue: #55 . It's not exactly same though; everything seems to build but there is an error during tests.

Thanks for this project!

@musoke
Copy link
Contributor Author

musoke commented Sep 3, 2017

Disabling https is a temporary work around: https://travis-ci.org/musoke/inspirer/builds/271306689

Possibly also related: seanmonstar/reqwest#70

musoke added a commit to musoke/inspirer that referenced this issue Sep 3, 2017
Disables https when accessing inspire.  Travis + trust seems to break
reqwest + SSL.
japaric/trust#81
@japaric
Copy link
Owner

japaric commented Sep 11, 2017

Interesting: the errors are not from running the cross command itself but from running the test suite within the cross / Docker environement. Hmm, maybe the ca-certficates inside the Docker images need to be updated. I can test that locally. If that works making a new Cross release should fix all the trust instances.

@japaric
Copy link
Owner

japaric commented Sep 21, 2017

I tried a few things here: just rebuilding the Docker image as it is, bumping the OpenSSL version, basing the Docker image on a more recent OS (12.04 -> 14.04) but I still see the same problem.

I must admit that I don't understand the root of the problem. A similar problem was reported in cross-rs/cross#119; in that case, a binary compiled with Cross doesn't work when executed on the host (not in the Cross environement) because it panics with some SSL related error.

@musoke
Copy link
Contributor Author

musoke commented Sep 23, 2017

Thanks for looking into this!

@StefanoChiodino
Copy link

Thanks @musoke, I too had this problem and worked around it adding to the Cargo.toml

[dependencies.libinspire]
git = "https://github.com/musoke/libinspire"
branch = "no-https"

@StefanoChiodino
Copy link

Spoke too soon! When I download the release file produced by travis I still get the same error!

StefanoChiodino pushed a commit to StefanoChiodino/niceprofit that referenced this issue Nov 7, 2017
@musoke musoke closed this as completed Jun 8, 2019
@musoke
Copy link
Contributor Author

musoke commented Jun 8, 2019

This issue seems to have been resolved. Don't know how or when.

StefanoChiodino pushed a commit to StefanoChiodino/niceprofit that referenced this issue Jan 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants