Hi,

we have enabled our portal ip address on the engine and hosts firewall but still the connection failed. so there should be no firewall issues.

-- 
Regards
Shanil

On Wed, Jul 16, 2014 at 3:26 PM, Shanil S <xielesshanil@gmail.com> wrote:

Hi Sven,

Regarding the ticket "path", Is it the direct combination of host and port ? suppose if the host is 1.2.3.4 and the port is 5100 then what should be the "path" value ? Is there encryption needs here ?

>>so you have access from the browser to the websocket-proxy, network
wise? can you ping the proxy?
and the websocket proxy can reach the host where the vm runs?

 yes.. there should be no firewall issue as we can access the console from ovirt engine portal

 Do we need to allow our own portal ip address in the ovirt engine and hypervisiors also ???

-- 
Regards
Shanil

On Wed, Jul 16, 2014 at 3:13 PM, Sven Kieske <S.Kieske@mittwald.de> wrote:

Am 16.07.2014 11:30, schrieb Shanil S:

> We will get the ticket details like host,port and password from the ticket
> api funcion call but didn't get the "path" value. Will it get it from the
> ticket details ? i couldn't find out any from the ticket details.

the "path" is the combination of host and port.

so you have access from the browser to the websocket-proxy, network
wise? can you ping the proxy?
and the websocket proxy can reach the host where the vm runs?
are you sure there are no firewalls in between?
also you should pay attention on how long your ticket
is valid, you can specify the duration in minutes in your api call.

--
Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen