<div dir="ltr">So I switched back to the original self-signed certs that I had luckily saved and was able to get in without error. Is there a new process for using non-self-signed certs with ovirt 4.0?<br><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">Thanks,</div><div class="gmail_signature" data-smartmail="gmail_signature">--<br>Matt Haught<br></div></div>
<br><div class="gmail_quote">On Fri, Jun 24, 2016 at 11:19 AM, Matt Haught <span dir="ltr"><<a href="mailto:dmhaught@ncsu.edu" target="_blank">dmhaught@ncsu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I just attempted an upgrade from 3.6 to 4.0 hosted engine and ran into an problem. The hosted engine vm updated without issue, but when I go to login to the web interface to continue the process I get:<div><br></div><div>sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target</div><div><br></div><div>at every page load and I can't login. I have a feeling that the issue comes from where I replaced the self-signed certs with trusted ca signed certs a year ago. Is there a work around?</div><div><br></div><div>CentOS 7.2</div><div><br></div><div>Thanks,<br clear="all"><div><br clear="all"><div><div data-smartmail="gmail_signature">--<br>Matt Haught<br></div></div>
</div>
</div></div>
</blockquote></div><br></div></div>