Skip to content

error: failed to fetch https://github.com/rust-lang/crates.io-index - Caused by: [16/-17] The SSL certificate is invalid #3344

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

Closed
gac55 opened this issue Nov 29, 2016 · 6 comments

Comments

@gac55
Copy link

gac55 commented Nov 29, 2016

I am using a dockerfile to build an environment with Rust. I have been using this as a base.
Error:
Updating registry `https://github.com/rust-lang/crates.io-index` error: failed to fetch `https://github.com/rust-lang/crates.io-index

It has previously functioned fine. What has changed to cause this?

Steps to reproduce -

Clone above repo and build via docker build -t "test:latest" /path/to/repo/

Edit, I added the verbose output and got the following:

Caused by: [16/-17] The SSL certificate is invalid

@gac55 gac55 changed the title error: failed to fetch https://github.com/rust-lang/crates.io-index error: failed to fetch https://github.com/rust-lang/crates.io-index - Caused by: [16/-17] The SSL certificate is invalid Nov 29, 2016
@apanda
Copy link

apanda commented Nov 29, 2016

I am seeing the same thing on Debian and on (Travis)[https://travis-ci.com/NetSys/NetBricks#L3392] with Rust nightly toolchain. This is not a problem when either using the nightly build from the 26th (through rustup default nightly-2016-11-26-x86_64-unknown-linux-gnu) or when using OS X.

@apanda
Copy link

apanda commented Nov 29, 2016

Seems to have also happened to some of the builds for #3342 e.g.,

@est31
Copy link
Member

est31 commented Nov 29, 2016

Dupe of #3340

@gac55
Copy link
Author

gac55 commented Nov 29, 2016

Thanks guys. Trying to understand how to rectify. Can you help me with what action I should take?

@est31
Copy link
Member

est31 commented Nov 29, 2016

As its fixed on master, I'd say you should wait until the next nightly, or alternatively, manually roll back the version on your travis setup. I see from reading the other issue that this workaround might fix it: #598 (comment)

@gac55
Copy link
Author

gac55 commented Nov 29, 2016

Thanking you.

Workaround - ENV SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt

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