Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Everything on this laptop goes through an outbound proxy. Browsers work, our internal tools work, the installer does not — it gets partway and then hangs until it gives up on the download.
Does it read proxy settings at all, or do I need to fetch things by hand?
Accepted answer
It honours HTTPS_PROXY, HTTP_PROXY and NO_PROXY, and so do curl, git and the package manager once those are exported. Export them in the same shell you run the installer from — not in your profile only, if you are testing in an already-open terminal.
export HTTPS_PROXY=http://proxy.corp.example:8080
export HTTP_PROXY="$HTTPS_PROXY"
export NO_PROXY=localhost,127.0.0.1,.corp.example
curl -fsSL https://sdods.com/install.sh | shIf a clone still fails after that, git needs telling separately — it does not always pick the variable up depending on how it was built:
git config --global http.proxy "$HTTPS_PROXY"Do not forget NO_PROXY. Sending localhost through the proxy is how people end up with an installer that works and a test run that cannot reach its own server.
One more thing that is easy to miss: if the proxy also inspects TLS you will get past the hang and into a certificate error instead. That is a different fix — you have to give the toolchain your internal CA bundle. Worth knowing before you conclude the proxy variables did not work.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.