I really seems to point to something strange that I've done with
my
certificates I guess..
I get the following on chrome
WebSocket server settings:
- Listen on *:6100
- Flash security policy server
- SSL/TLS support
- proxying from *:6100 to targets in /dummy
1: handler exception: WSRequestHandler instance has no attribute 'last_code'
and the following on firefox:
[root@bluejay X86]# - proxying from *:6100 to targets in /dummy
1: handler exception: WSRequestHandler instance has no attribute 'last_code'
2: handler exception: [Errno 1] _ssl.c:1390: error:14094412:SSL
routines:SSL3_READ_BYTES:sslv3 alert bad certificate
3: handler exception: [Errno 1] _ssl.c:1390: error:14094412:SSL
routines:SSL3_READ_BYTES:sslv3 alert bad certificate
4: handler exception: [Errno 1] _ssl.c:1390: error:14094419:SSL
routines:SSL3_READ_BYTES:tlsv1 alert access denied
5: handler exception: [Errno 1] _ssl.c:1390: error:14094419:SSL
routines:SSL3_READ_BYTES:tlsv1 alert access denied
6: handler exception: [Errno 1] _ssl.c:1390: error:14094419:SSL
routines:SSL3_READ_BYTES:tlsv1 alert access denied
is there a way to just turn off SSL websockets for now?
On Fri, Apr 18, 2014 at 9:24 AM, Jeremiah Jahn
<jeremiah(a)goodinassociates.com> wrote:
> Even after I've manually imported the ca.cert file into both chrome
> and firefox, I get the same error as before. Is there something that
> needs to be done on each host? I installed the websocket-proxy after
> the fact, and each host is a manually installed host, as opposed to
> the node.iso install.
>
> On Fri, Apr 18, 2014 at 8:28 AM, Jeremiah Jahn
> <jeremiah(a)goodinassociates.com> wrote:
>> And yet I always seem to get this error:
>>
>> WebSocket connection to
>>
'wss://localhost:6100/eyJ2YWxpZFRvIjoiMjAxNDA0MTgxMzI4MjMiLCJkYXRhIjoiJTdCJT...lHbjZVRHhzOThaRndVdUlmM0s5Wk1VQVh4K2QwZz09Iiwic2FsdCI6IjlxZFkzakN4U0lNPSJ9'
>> failed: WebSocket is closed before the connection is established.
>> spicehtml5-main.html?host=localhost&port=6100:1
>> << disconnect spicehtml5-main.html?host=localhost&port=6100:90
>> Error in event handler for (unknown): TypeError: Cannot read property
>> 'state' of null at CSRecorder.onQueryStateCompleted
>>
(chrome-extension://cplklnmnlbnpmjogncfgfijoopmnlemp/content_scripts/recorder.js:43:13)
>> at extensions::messaging:327:9 at Function.target.(anonymous function)
>> (extensions::SafeBuiltins:19:14) at Event.dispatchToListener
>> (extensions::event_bindings:386:22) at Event.dispatch_
>> (extensions::event_bindings:371:27) at Event.dispatch
>> (extensions::event_bindings:392:17) at dispatchOnMessage
>> (extensions::messaging:294:22)
>> spicehtml5-main.html?host=localhost&port=6100:1
>>
>> On Thu, Apr 17, 2014 at 6:21 PM, Maurice James <mjames(a)media-node.com>
wrote:
>>> There are a few steps. Download the CA cert from your manager
>>> https://<ovirtaddress>/ca.crt
>>> Make sure it is trusted.
>>> Make sure ovirt-webproxy-socket is installed and running.
>>>
>>> Sent from my Galaxy S(R)III
>>>
>>>
>>> -------- Original message --------
>>> From: Jeremiah Jahn
>>> Date:04/17/2014 9:56 AM (GMT-05:00)
>>> To: users(a)ovirt.org
>>> Subject: [ovirt-users] is spice html5 console actually working
>>>
>>> Has anyone gotten the html5 spice console to work, and did you have to
>>> do anything special other than enable it? I've tried every browser
>>> except opera and ie on linux and mac
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>>
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users