Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm setting up an environment with juju and maas. The maas environment has no direct internet connection, a proxy must be used.

I have configured the juju environment's proxy using juju set-env http-proxy=http://my_proxy:8080 and that works, however, when deploying somehting like keystone, there is an installation hook that tries to access localhost, and this request is trying to also go though the proxy.

I have tried juju set-env no-proxy or juju set-env no_proxy, but the debug log just shows there is no config field with either name.

Is there a way to set a no proxy list, and should local addresses bypass the proxy by default?

share|improve this question

Full support for proxies was added with the 1.18.0 release of Juju.

From the release notes:

Support for proxies

Proxies can now be configured for the providers in the environments.yaml file, or added to an existing environment using "juju set-env" The configuration options are:


The protocol-specific options accept a URL. The "no-proxy" option accepts a comma-separated list of host names or addresses.

The proxy options are exported in all hook execution contexts, and also available in the shell through "juju ssh" or "juju run".

There are three additional proxy options specific for apt. These are set to be the same as the non-apt proxy values, but can be overridden independently:


For example, with a squid-deb-proxy running on a laptop, you can specify the apt-http-proxy to use it for the containers by specifying the host machine’s network-bridge:

share|improve this answer

I was facing similar issues on a devstack installation of openstack. It seems like the variable is case sensitive. To solve this I did the following:

Get your ipaddress using the following:


and open your ~/.bashrc file, add this to the end:


and then open a new terminal or do source ~/.bashrc.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.