Comment 1 for bug 1563067

This is probably a duplicate of #1556207 and I have a fix landing for that at the moment in the 1.25 branch. It will then be forward ported to 2.0.

The specific problem of not being able to download a charm is because the juju clients try to download it via the API server, but the API server isn't on the no_proxy list, so it goes to the proxy, which can't see the API server...

You can find what Juju has set its proxy settings are by looking on any Juju deployed machine at ~/.juju-proxy. If you source that file (as generated by the current Juju binary) and wget works on a Juju machine that isn't machine 0 before I land my fix then this is a different problem.