This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.
Chrome Extension not connecting to agent
I realize you don't support non-stable builds of Chrome, but I just want to give you guys a heads up as it appears the connectivity in the devel version of Chrome is broken (and has been for the past week or so). I found the error in the 1Password agent log:
[CODE]16:25:21 [ INFO] T1pAgent: Connecting to 127.0.0.1
16:25:21 [ INFO] TWebSocketConnection: Handshake: RcvdCount: 308
16:25:21 [ INFO] TWebSocketConnection: Handshake: GET /2 HTTP/1.1
16:25:21 [ INFO] TWebSocketConnection: Handshake: Upgrade: websocket
16:25:21 [ INFO] TWebSocketConnection: Handshake: Connection: Upgrade
16:25:21 [ INFO] TWebSocketConnection: Handshake: Host: 127.0.0.1:6258
16:25:21 [ INFO] TWebSocketConnection: Handshake: Origin: chrome-extension://gkndfifopckmhdkohjeoljlbfnjhekfg
16:25:21 [ INFO] TWebSocketConnection: Handshake: Pragma: no-cache
16:25:21 [ERROR] TWebSocketConnection: EWebSocketHandshakeException: Sec-WebSocket-Key1 missing from handshake (Pragma: no-cache): Cache-Control: no-cache Sec-WebSocket-Key: n2Ac3A9DTRWPov1opHkNGw== Sec-WebSocket-Version: 13 Sec-WebSocket-Extensions: x-webkit-deflate-frame
16:25:21 [ INFO] T1pAgent: Disconnecting from 127.0.0.1
16:25:21 [ INFO] T1pSocketClient: 006F03C0 TCustomWSocket.Shutdown 1 448[/CODE]
Hope that helps!
--Steve
[CODE]16:25:21 [ INFO] T1pAgent: Connecting to 127.0.0.1
16:25:21 [ INFO] TWebSocketConnection: Handshake: RcvdCount: 308
16:25:21 [ INFO] TWebSocketConnection: Handshake: GET /2 HTTP/1.1
16:25:21 [ INFO] TWebSocketConnection: Handshake: Upgrade: websocket
16:25:21 [ INFO] TWebSocketConnection: Handshake: Connection: Upgrade
16:25:21 [ INFO] TWebSocketConnection: Handshake: Host: 127.0.0.1:6258
16:25:21 [ INFO] TWebSocketConnection: Handshake: Origin: chrome-extension://gkndfifopckmhdkohjeoljlbfnjhekfg
16:25:21 [ INFO] TWebSocketConnection: Handshake: Pragma: no-cache
16:25:21 [ERROR] TWebSocketConnection: EWebSocketHandshakeException: Sec-WebSocket-Key1 missing from handshake (Pragma: no-cache): Cache-Control: no-cache Sec-WebSocket-Key: n2Ac3A9DTRWPov1opHkNGw== Sec-WebSocket-Version: 13 Sec-WebSocket-Extensions: x-webkit-deflate-frame
16:25:21 [ INFO] T1pAgent: Disconnecting from 127.0.0.1
16:25:21 [ INFO] T1pSocketClient: 006F03C0 TCustomWSocket.Shutdown 1 448[/CODE]
Hope that helps!
--Steve
Flag
0
Comments
-
Thanks for the heads up, Steve! This is a known issue, but we really appreciate you mentioning it. As you hinted at, the solution is to stick with the supported stable build of Chrome. It can be tricky to hit a moving target and even the beta builds are pretty wiggly sometimes. <img src='http://forum.agilebits.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />
We'll definitely have this resolved by the time Chrome 24 is in the stable channel, and hopefully even sooner.Flag 0 -
Fixed in 1.0.9.BETA-303Flag 0
-
You guys rock! Thanks for getting this fixed so quickly.Flag 0