On 02/02/2015 01:27 PM, Mathieu Gagné wrote:
On 2015-02-02 11:36 AM, Chris Friesen wrote:
On 01/30/2015 06:26 AM, Jesse Pretorius wrote:
Have you tried manually updating the NoVNC and websockify files to later
versions from source?
We were already using a fairly recent version of
On 01/30/2015 06:26 AM, Jesse Pretorius wrote:
On 29 January 2015 at 04:57, Chris Friesen chris.frie...@windriver.com
mailto:chris.frie...@windriver.com wrote:
On 01/28/2015 10:33 PM, Mathieu Gagné wrote:
On 2015-01-28 11:13 PM, Chris Friesen wrote:
Anyone have any
On 2015-02-02 11:36 AM, Chris Friesen wrote:
On 01/30/2015 06:26 AM, Jesse Pretorius wrote:
Have you tried manually updating the NoVNC and websockify files to later
versions from source?
We were already using a fairly recent version of websockify, but it
turns out that we needed to upversion
On 29 January 2015 at 04:57, Chris Friesen chris.frie...@windriver.com
wrote:
On 01/28/2015 10:33 PM, Mathieu Gagné wrote:
On 2015-01-28 11:13 PM, Chris Friesen wrote:
Anyone have any suggestions on where to start digging?
We have a similar issue which has yet to be properly diagnosed on
Is SSL involved anywhere from the client browser to the server ?
Is there any load balancing ? Which load balancer software ?
--
David Moreau Simard
On 2015-01-28, 11:57 PM, Chris Friesen chris.frie...@windriver.com
wrote:
On 01/28/2015 10:33 PM, Mathieu Gagné wrote:
On 2015-01-28 11:13 PM,
Hi all,
I'm playing around with nova (current trunk) and I've hit an odd issue.
I can get the novnc console for instances to show up on iceweasel 31.3.0, but it
doesn't work in konqueror, internet explorer, or firefox 31.0. Anyone got any
ideas where to start digging?
In the problematic
On 2015-01-28 11:13 PM, Chris Friesen wrote:
Anyone have any suggestions on where to start digging?
We have a similar issue which has yet to be properly diagnosed on our side.
One workaround which looks to be working for us is enabling the private
mode in the browser. If it doesn't work,
On 01/28/2015 10:33 PM, Mathieu Gagné wrote:
On 2015-01-28 11:13 PM, Chris Friesen wrote:
Anyone have any suggestions on where to start digging?
We have a similar issue which has yet to be properly diagnosed on our side.
One workaround which looks to be working for us is enabling the
