There is a really easy fix for that: Get a real certificate from a real CA. You should not use self-signed certs for a production environment.
Greetings Wilma 2014-02-06 ML mail <[email protected]>: > This workaround fixes that problem yes but it is not a good workaround > especially if you want to offer opennebula to real customers. I hope > another better alternative can be found in the future but I am aware that > this is mostly a browser problem :| > > Regards > ML > > > > On Thursday, February 6, 2014 10:56 AM, Daniel Molina < > [email protected]> wrote: > Hi, > > > On 5 February 2014 16:58, ML mail <[email protected]> wrote: > > Hello, > > I would like to use noVNC in Sunstone over an encrypted channel (WSS). > Therefore I have generated my own SSL key and certificate which I have > added to the sunstone-server.conf configuration. The problem is that this > does not work, when I start VNC from the Sunstone web interface I get the > following error message in novnc.log: > > SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca > > Does this mean I need an official SSL certificate? > > > Please, check if the solution proposed in this thread, fixes your problem > > http://lists.opennebula.org/pipermail/users-opennebula.org/2014-February/026405.html > > Cheers > > > > Regards > > ML > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > > > > -- > -- > Daniel Molina > Project Engineer > OpenNebula - Flexible Enterprise Cloud Made Simple > www.OpenNebula.org <http://www.opennebula.org/> | [email protected]| > @OpenNebula > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
