我使用Websockify通过noVNC连接到VNC Server (TightVNC)。这在Firefox 14.0.1,Chrome 21,甚至IE 10上运行得很好。现在我升级到Firefox 15,问题开始了:
这是websockify的示例输出:
>websockify.exe 6080 localhost:5900 -v
WARNING: no 'resource' module, daemonizing support disabled
WebSocket server settings:
- Listen on :6080
- Flash security policy server
- No SSL/TLS support (no cert file)
- proxying from :6080 to localhost:5900
#Connection with Chrome
1: 79.194.220.16: Plain non-SSL (ws://) WebSocket connection
1: 79.194.220.16: Version hybi-13, base64: 'True'
1: connecting to: localhost:5900
Traffic Legend:
} - Client receive
}. - Client receive partial
{ - Target receive
> - Target send
>. - Target send partial
< - Client send
<. - Client send partial
{<}>{<}>{<}>{<}>{<}>{{<<}>}>{}><}>}>}>}> 1: localhost:5900: Target closed
1: 79.194.220.16: Client closed, reason: None - None
#Chrome disconnected, Firefox tries to connect
2: 79.194.220.16: ignoring socket not ready
3: 79.194.220.16: Plain non-SSL (ws://) WebSocket connection
3: 79.194.220.16: Version hybi-13, base64: 'True'
3: connecting to: localhost:5900
Traffic Legend:
} - Client receive
}. - Client receive partial
{ - Target receive
> - Target send
>. - Target send partial
< - Client send
<. - Client send partial
{<在最后一行websockify挂起后,不接受任何其他连接。以下是来自Firefox的控制台输出:
New state 'loaded', was 'disconnected'. Msg: noVNC ready: native WebSockets, canvas rendering
util.js (Zeile 110)
New state 'connect', was 'loaded'.
util.js (Zeile 110)
WebSocket on-error event
util.js (Zeile 110)
New state 'failed', was 'connect'. Msg: Connect timeout
case 'error': Util.Error = function (msg) { console.error(msg); };
util.js (Zeile 111)
Firefox kann keine Verbindung zu dem Server unter ws://ec2-176-34-194-149.eu-west-1.compute.amazonaws.com:6080/websockify aufbauen.
websocket = new WebSocket(uri, 'base64');
websock.js (Zeile 275)
WebSocket on-close event
util.js (Zeile 110)
Received onclose while disconnected (code: 1006)
case 'error': Util.Error = function (msg) { console.error(msg); };
util.js (Zeile 111)
New state 'disconnected', was 'failed'.如上所述,这在FF 14.0.1中工作得很好,在Chrome 21和IE 10中仍然有效。
你知道为什么Firefox会使用websockify吗?这是Firefox Websocket代码中的错误还是Websockify中的错误?
发布于 2012-09-06 22:21:59
我已经回复了你的Mozilla bug报告:https://bugzilla.mozilla.org/show_bug.cgi?id=789018
总而言之,这是一个Windows/python问题,加上firefox 15中的一个错误功能(推测性连接)。
作为临时解决方案,您可以在noVNC中增加连接超时。
https://stackoverflow.com/questions/12299353
复制相似问题