Hot answers tagged proxy
The error message for this problem was correct, the server was in restricted network and did not have access to the Internet. The lab has a proxy server for http and https traffic. The solution was to export http_proxy, https_proxy, and no_proxy environment variables on the Juju host server: export http_proxy=http://squid.internal:3128 export ...
I'm not sure about all the downloads that you are seeing but at least lxc images are retrieved over HTTPS so will not be cacheable. See: https://email@example.com/msg01303.html
Not sure what might have happened to your system, but you may be interested in setting those in your terminal/commandline: export http_proxy="http://user:password@proxy_server:port" export https_proxy="https://user:password@proxy_server:port" Can you actually check what shows: echo $http_proxy (btw - you may use this way for ftp_proxy, too)
The best my google-goo can offer is https://juju.ubuntu.com/docs/howto-proxies.html https://juju.ubuntu.com/docs/howto-offline-charms.html
I guess openconnect configures http proxy to be used by FF. ('Connection through HTTP proxy, including libproxy support for automatic proxy configuration.') FF Preferences - Advanced - Network etc, you should exclude localhost. Another option is a change of resolv.conf that will redirect even localhost. cat it. I'd try wget -vvv and see exact step ...
if your wireless card supports Station (aka "infrastructure" ) mode or Access point mode (STA and AP respectively) it can be used to create a hotspot. For more information, have a look at kernel.org's excellent documentation The easiest command to show what you've currently got is sudo iw list | grep --after-context=5 "interface mode" The settings you are ...
The installer sets apt-http-proxy to whatever your MAAS server IP is for an existing MAAS installation. So whenever juju deploys any services which require apt-get installs it'll pull from that proxy.
Only top voted, non community-wiki answers of a minimum length are eligible