Comment 19 for bug 1149410

Brian, can you do me a favor and check out the network inspector tool of the browser in your scenario? The client you load the GUI from needs to be able to login/pull down the JS from the GUI charm, however it also needs to talk on other ports as it holds a websocket connection to the juju state server. If the screen is spinning that it's unable to connect to the environment, I suspect the proxy is not proxying the secure websocket connection through to the juju state server.

A look at the network tab while loading the GUI should show the websocket connection attempting but failing.