On 03/06/2013 09:02 AM, Marius B. Kotsbak wrote:
> It tries to connect to the "ws" endlessly yes. The elastic IP was set up
> for another node. But I tried locally from the machine:
>
> $ wget http://localhost:8080/ws
...
wget is not designed to talk to a websocket connection, so it's not a
surprise that this doesn't work. Your output does show that something
is listening.
Could you try looking for the websocket url as I described? Go to
/juju-ui/assets/config.js on the GUI's public address. "socket_url" will
show a URL that cannot resolve from where you are. If that is true, the
temporary hack should work for you, and the fix we plan should be the
longer term solution.
On 03/06/2013 09:02 AM, Marius B. Kotsbak wrote: localhost: 8080/ws
> It tries to connect to the "ws" endlessly yes. The elastic IP was set up
> for another node. But I tried locally from the machine:
>
> $ wget http://
...
wget is not designed to talk to a websocket connection, so it's not a
surprise that this doesn't work. Your output does show that something
is listening.
Could you try looking for the websocket url as I described? Go to assets/ config. js on the GUI's public address. "socket_url" will
/juju-ui/
show a URL that cannot resolve from where you are. If that is true, the
temporary hack should work for you, and the fix we plan should be the
longer term solution.
Gary