-
Notifications
You must be signed in to change notification settings - Fork 949
rustup (and cargo) unable to get local issuer certificate #2924
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
Comments
Downloaded the install script and run with -v:
|
running cargo with strace I found out that cargo tries to search certs in /usr/local/ssl/certs
a listing of that directory returns it's empty:
In general, if I search for a file called |
It seems that the SSL connection to remote does not work because of missing peer and client certificates |
Update from my side (I will also close the ticket). I involved the openSuSE support and found out there was a second openssl installation in
|
Thank you @tsmt09 for letting us know what the solution was - hopefully this will help others who encounter similar looking issues. |
Had the same issue, I installed an old version of OpenSSL to get the Linux port of Garry's Mod working, but apparently that broke Rustup. I guess I'll have to stick it in a path that isn't automatically picked up. |
moving/usr/local/ssl to /root/backup/openssl/ worked for me. Did you end up deleting the backup folder, /root/backup/openssl/, afterwards? |
I ended up here because i had a matching error message as in these comments but my issue was that I had set |
It seems i have roughly the same error. But i'm at home / in local, without any proxy + certificates are up to date on my (archlinux) system. If i launch it manually in debut (outside AUR installation through YAY), then i see :
Again, my certificates (ca-certificates, etc.) are 100% installed ... Any ideas ? (this is nearly the only error i found about that "UnknownIssuer") |
@SR-G I have seen a similar issue in our CI (#3810) and it has been resolved exactly by installing the CA certs. It is also possible that your browser uses a different CA cert configuration than your CLI as discussed above... I'm not quite sure. So many local states are involved here, it seems to me. cc @djc |
Mhh ok but still not sure how to solve that ... Also, from the same CLI than where rustup is failing, a CURL or WGET (against the URL used by rustup) is perfectly working ...
It's like rustup was not using that /etc/ssl/certs path on ARCHLINUX, maybe ? |
Which version of rustup are you using? Can you run it with Also please just file a new issue instead of reusing this closed one. |
"rustup" is installed on my system with AUR package, so should be up-to-date (i would say) :
(second one is of course a folder) Ok opening a new issue. Done : #4325 |
Problem
Hey. I'm facing a similar problem as #2878:
When trying to install rust using the recommended shell command from here
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
I face the same error saying "unable to get local issuer certificate".I tried to install rustup via my distributions package then, and this worked pretty well. Now, trying to use cargo brings me to the exact same error "unable to get local issuer certificate".
I'm happy to help as good as I can. Rust for me is just a hobby beside my job so I'll be happy trying to get it fixed since I don't have any dependencies that it has to work again soon. Shoot me with any debugging info I'm happy to provide anything.
The issue also appearing in cargo when installing via distro package manager (zypper), I guess it's not really a rustup or cargo problem, but more of a os-certificate-store vs rust-server-certificate problem. I'm pretty sure this has something to do with the openSuSE Tumbleweed and will ask in their discord as soon as I can, but I just wanted to report that the error happened again because @kinnison asked do to so in the other issue. If I find an answer in discord I will provide it here of course.
Steps
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
Possible Solution(s)
No response
Notes
No response
Rustup version
rustup 1.24.3 (ce5817a94 2021-05-31)
Installed toolchains
The text was updated successfully, but these errors were encountered: