vko.se...@srce.hr<mailto:sasa.drnje...@srce.hr>, tel: +385 1 616 5807,
fax: +385 1 616 5559
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of
Stefano Danzi
Sent: Friday, February 20, 2015 9:08 AM
To: Darrell Budic
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Unable
ell Budic"
>> To: "Simone Tiraboschi"
>> Cc: "users"
>> Sent: Friday, February 20, 2015 5:57:10 PM
>> Subject: Re: [ovirt-users] Unable to run noVNC console un recent browsers
>>
>> I had some trouble with self signed cert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20.02.2015 18:50, Simone Tiraboschi wrote:
> The websocket proxy cert is not self-signed: it's normally signed
> by the internal oVirt CA.
imho this qualifies as a "self signed" certificate,
meaning it is not included in default trustores like
brows
- Original Message -
> From: "Darrell Budic"
> To: "Simone Tiraboschi"
> Cc: "users"
> Sent: Friday, February 20, 2015 5:57:10 PM
> Subject: Re: [ovirt-users] Unable to run noVNC console un recent browsers
>
> I had some trouble wi
t; From: "Donny Davis"
>> To: "Simone Tiraboschi"
>> Cc: users@ovirt.org
>> Sent: Friday, February 20, 2015 3:53:04 PM
>> Subject: RE: [ovirt-users] Unable to run noVNC console un recent browsers
>>
>> No, I made my life easy and used nginx to
browsers
- Original Message -
> From: "Donny Davis"
> To: "Simone Tiraboschi"
> Cc: users@ovirt.org
> Sent: Friday, February 20, 2015 3:53:04 PM
> Subject: RE: [ovirt-users] Unable to run noVNC console un recent
> browsers
>
> No, I made
- Original Message -
> From: "Donny Davis"
> To: "Simone Tiraboschi"
> Cc: users@ovirt.org
> Sent: Friday, February 20, 2015 3:53:04 PM
> Subject: RE: [ovirt-users] Unable to run noVNC console un recent browsers
>
> No, I made my life easy and
noVNC works without issue.
DonnyD
-Original Message-
From: Simone Tiraboschi [mailto:stira...@redhat.com]
Sent: Friday, February 20, 2015 7:03 AM
To: Donny Davis
Subject: Re: [ovirt-users] Unable to run noVNC console un recent browsers
- Original Message -
> From: "Donny
I used ip , FQDN and hostname.
The only way to make it work was downgrading Firefox
Il 20/02/2015 14.27, Donny Davis ha scritto:
Also are you use the ip address, or the FQDN for the engine in the browser?
I have issues with noVNC using the ip address of the engine even if the cert
is trusted.
D
Sent: Friday, February 20, 2015 5:57 AM
To: Stefano Danzi
Cc: users@ovirt.org
Subject: Re: [ovirt-users] Unable to run noVNC console un recent browsers
- Original Message -
> From: "Stefano Danzi"
> To: "Darrell Budic"
> Cc: users@ovirt.org
> Sent: Frid
- Original Message -
> From: "Stefano Danzi"
> To: "Darrell Budic"
> Cc: users@ovirt.org
> Sent: Friday, February 20, 2015 9:07:51 AM
> Subject: Re: [ovirt-users] Unable to run noVNC console un recent browsers
>
> Hello!
> Already do
Hello!
Already done but this didn't help.
I downloaded a portable version of Firefox 17 and noVNC work as expected.
Il 20/02/2015 5.18, Darrell Budic ha scritto:
Try reimporting the ca.cert for noVNC by connecting directly to the webproxy
address at port 6100. Do this by trying to connect to a
Try reimporting the ca.cert for noVNC by connecting directly to the webproxy
address at port 6100. Do this by trying to connect to a console and then, once
the 1006 error shows up, just strip off everything after :6100/ . I've found
that somewhere in or after 3.5, restarting the webproxy causes
Hello,
I can't make work noVNC console on recent browsers (Chrome 40, Firefox
35 and IE 11).
The error that I have is already explained here:
https://forge.univention.org/bugzilla/show_bug.cgi?id=33587
I tried to change websocket like suggested
(http://errata.univention.de/ucs/3.2/31.html)
14 matches
Mail list logo
