Hello, for running spice-html5 and novnc you also must update certificates in your browser - it means you must add the certificate that websocket proxy uses (SSL_CERTIFICATE in the config file) to the browser (or trust the CA of the engine). Could you try adding it? Thanks, Frank. ----- Original Message ----- From: "lof yer" <lofyer@gmail.com> To: "users" <users@ovirt.org> Sent: Friday, July 12, 2013 11:07:57 AM Subject: [Users] Cannot connect via spice-html5. & How to use noVnc? Here's my ovirt-websocket-proxy's status when I open the spice-html5 client ovirt-websocket-proxy.service - oVirt Engine websockets proxy Loaded: loaded (/usr/lib/systemd/system/ovirt-websocket-proxy.service; enabled) Active: active (running) since Fri 2013-07-12 17:03:46 CST; 31s ago Main PID: 19226 (ovirt-websocket) CGroup: name=systemd:/system/ovirt-websocket-proxy.service └─19226 /usr/bin/python /usr/share/ovirt-engine/services/ovirt-websocket-proxy.py start Jul 12 17:03:46 engine systemd[1]: Started oVirt Engine websockets proxy. Jul 12 17:04:01 engine ovirt-websocket-proxy.py[19226]: WebSocket server settings: Jul 12 17:04:01 engine ovirt-websocket-proxy.py[19226]: - Listen on *:6100 Jul 12 17:04:01 engine ovirt-websocket-proxy.py[19226]: - Flash security policy server Jul 12 17:04:01 engine ovirt-websocket-proxy.py[19226]: - SSL/TLS support Jul 12 17:04:01 engine ovirt-websocket-proxy.py[19226]: - Deny non-SSL/TLS connections Jul 12 17:04:01 engine ovirt-websocket-proxy.py[19226]: - proxying from *:6100 to targets in /dummy Jul 12 17:04:01 engine ovirt-websocket-proxy.py[19226]: 1: handler exception: WSRequestHandler instance has no attribute 'last_code' _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users