Comment 3 for bug 1563067

Kevin - it could be the case that since you set the proxy information once the controller was bootstrapped, that those proxy changes didn't get applied to the currently running jujud processes. You can see this comment for some background: https://bugs.launchpad.net/juju-core/+bug/1556207/comments/15

We can see if that's the case by setting the proxy information in the config during bootstrap (either with --config http-proxy=<url>, etc., or by passing in a yaml file with the proxy info). If you do that, does it work for you?