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

Download toolchains from behind a proxy #35

Closed
XAMPPRocky opened this issue Nov 12, 2015 · 10 comments
Closed

Download toolchains from behind a proxy #35

XAMPPRocky opened this issue Nov 12, 2015 · 10 comments

Comments

@XAMPPRocky
Copy link
Member

I'm currently behind a proxy, and can't download any toolchains. How do you set up proxy settings with multirust?

@mkpankov
Copy link

@Aaronepower do you have http_proxy and https_proxy set up?

@XAMPPRocky
Copy link
Member Author

I'm on Windows forgot to say. But I do also have those set up as env variables.

On Thu, Nov 12, 2015 at 12:34 PM, Michael Pankov notifications@github.com
wrote:

@Aaronepower do you have http_proxy and https_proxy set up?

Reply to this email directly or view it on GitHub:
#35 (comment)

@kikokikok
Copy link

Hi,

Any news on this issue, I can't use multirust because of a enterprise proxy. Is there any workaround ?
Thanks !

@lilianmoraru
Copy link

Same issue here. I am on Ubuntu 15.10, 64-bit.
I have http_proxy, https_proxy and ftp_proxy set up.
multirust - the script, picks them up and the command multirust update works.
multirust-rs - the Rust application, doesn't work with the proxy.

info: updating existing install for 'beta'
downloading file from: 'https://static.rust-lang.org/dist/channel-rust-beta.sha256'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-beta.sha256' to '/home/uidr1070/.multirust/tmp/tfr6k8vxppx6ngcd_file' (Network: connection refused)
info: updating existing install for 'nightly'
downloading file from: 'https://static.rust-lang.org/dist/channel-rust-nightly.sha256'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-nightly.sha256' to '/home/uidr1070/.multirust/tmp/x07lpef1zc6s24vr_file' (Network: connection refused)
info: updating existing install for 'stable'
downloading file from: 'https://static.rust-lang.org/dist/channel-rust-stable.sha256'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-stable.sha256' to '/home/uidr1070/.multirust/tmp/pr1qo3_cbbj0tk5g_file' (Network: connection refused)

   beta update FAILED
nightly update FAILED
 stable update FAILED

@lilianmoraru
Copy link

Tried today rustup and the issue is still present.
I had issues installing it(multirust-rs was installing over multirust but it doesn't any more - another issue):

Continue? (Y/n) Y

error: toolchain 'nightly' is not installed
rustup: command failed: /tmp/tmp.pHwfFAkit0/rustup-setup

To solve the issue I had to run multirust uninstall command(I tried removing the toolchains, then the metadata, finally after removing multirust it worked).

After this, I tried to install rustup:

Continue? (Y/n) 
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-stable.toml.sha256' to '/home/uidr1070/.multirust/tmp/zo5drrtemgah7y1s_file' (Network: connection refused)
rustup: command failed: /tmp/tmp.sr3f0QCId8/rustup-setup

@xen0n
Copy link
Contributor

xen0n commented Apr 25, 2016

Waiting on this too, but according to #344 this bug should be fixed shortly.

@alexcrichton
Copy link
Member

This should now be done! With the switch to curl in #434 rustup should naturally pick up the relevant env vars now.

@lilianmoraru
Copy link

I'll test when I go back to work and report the results.

@xen0n
Copy link
Contributor

xen0n commented May 15, 2016

Just updated to latest rustup, proxies confirmed working!

@lilianmoraru
Copy link

I can confirm that the behavior seems to be the same as with cargo.

  • Works through a proxy
  • Doesn't work through WPAD

All tools have problems running in cmd because of WPAD, so I guess this is the expected behavior :)

djc added a commit that referenced this issue Jun 18, 2024
# This is the 1st commit message:

Port cli_inst_interactive to CliTestContext

# The commit message #2 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #3 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #4 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #5 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #6 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #7 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #8 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #9 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #10 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #11 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #12 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #13 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #14 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #15 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #16 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #17 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #18 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #19 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #20 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #21 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #22 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #23 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #24 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #25 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #26 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #27 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #28 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #29 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #30 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #31 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #32 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #33 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #34 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #35 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #36 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #37 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #38 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #39 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext

# The commit message #40 will be skipped:

# fixup! Port cli_inst_interactive to CliTestContext
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

6 participants