-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Fails behind corporate proxy (but plain cargo install works) #250
Comments
Hm. It looks like, to the extent of, cargo-update talking to the network, it did work – polling the registry completed, this output matches reality. The step that failed is the updating step, i.e. fork()/exec("cargo", "[b]install", ...) – all the logs since Given the formatting and them containing three 2kB blobs, I'd assume cargo-binstall, especially since you say |
Hmmm it seems that cargo-binstall has problem dealing with your transparent proxy setup. Would you please open a ticket in cargo-binstall and gives us the info required to reproduce/fix this? Thanks! |
I don't believe it is cargo-bininstall. It seems to apply to all packages I build via "cargo install-update" as opposed to "cargo install". Cargo-bininstall was just the example I pasted above. |
Can you try using |
Oh, didn't know that. I can try when I get back to the office. Right now it is hard to try: 1) everything is up-to-date 2) I'm working remotely today rather than at the office (and it only happens when in the office for some reason). But I do find the line |
You can use P.S. it's
Could you please open an issue in |
Actually I already have a hint on what went wrong. Would open a PR tomorrow |
Opened cargo-bins/cargo-binstall#1589 for this, it should fix the issue for you. |
Thanks I will check it out today when I'm at the office. |
I had nothing that needed updating, but |
I'm behind a corporate transparent HTTPS proxy. The required SSL certificate has been installed in /etc/ca-certificates and works as expected for plain
cargo install
. However:As I said above, running a plain
cargo install cargo-binstall
works perfectly. It seems cargo-update does not respect the system certificate store.System & environment info:
The text was updated successfully, but these errors were encountered: