<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 11, 2017 at 9:18 PM, summit hainey <span dir="ltr"><<a href="mailto:s.hainey@protonmail.ch" target="_blank">s.hainey@protonmail.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>I believe I have setup the engine as a proxy, during the initial
install, unless I'm remembering incorrectly, or misread something.<br></div><div><br></div><div>I
ended up at least being able to connect using the "Native" client
option, apparently, the TLS port was not being forwarded by default in
the firewall settings oVirt setup during install. I got the console to
work after opening the port and saving the .vv, and then running it
manually, however this is not a good long term solution for my
situation... ideally I'd like to get one or both of the browser clients
working.<br></div></div><div><br></div><div><div>I think the issue may be one of three
things, a cert issue, but I don't know how likely that is. Obviously I
get an invalid cert issue from whatever browser I access oVirt with
since it's just using the default local certs, but I've allowed them on
both Firefox and Chromium, and I've gotten a websocket console to work
in different management platforms (kimchi), however I read somewhere in
my search that oVirt uses two certs, one for the main part of the
client, and then another for websockets, however I don't know if this is
accurate.<br></div></div></blockquote><div><br></div><div>you need to import the engine CA into the browser, not only the certificate.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div><br></div><div>The other thing I suspect is that it could be another
port/firewall related issue, although I cannot see what port it could
be, and I have no real hints to go on.<br></div></div></blockquote><div><br></div><div>here the clients need to go through websocket proxy which is a different service running somewhere, most typically on engine. Please check it is up and running and reachable<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div></div><div><br></div><div><div>Lastly I imagine the proxy could be ill-configured, but I don't know how seeing as everything is essentially set to default.<br></div><div><br></div><div>Actually,
I just thought of another possibility though it seems like a bit of a
stretch, but I'm running the oVirt host and the engine on the same
machine, but not in a hosted-engine setup.<br></div></div><div><br></div><div>That's the best I've got, though.<br></div><br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>