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 it to generate its own new ca.cert even through it shouldn't.
-Darrell > On Feb 19, 2015, at 4:09 PM, Stefano Danzi <[email protected]> wrote: > > 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) but this not helped. > > Someone know a workaround? > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
