stuicey

Yeah, its trivial to update this for use with websockify ([see here](https://github.com/stuicey/SSHy/issues/4)), I'd be hesitant to make it part of the normal release though unless websockify or another major websocket...

Seems related to https://github.com/stuicey/SSHy/issues/18 Can you make sure you've installed the correct version of wsproxy?

Looks like something might have gone wrong in KEX since the client is forcing a disconnection `debug3: receive packet: type 1 [preauth]` Probably easier to debug if you can provide...

Not sure I entirely understand the scenario you've laid out but can get the general gist of it. The wrapper version of this seems to be what you'd want to...

Are you positive you've used the forked version of wsproxy? I know its fumbled a couple people in the past where they've used the normal version. All wsproxy does is...

Odd then, I would expect '`String contains an invalid character`' to come out if you were using the other version. Do you get anything if you try `console.log(e.data)` instead of...

Have you looked in the javascript console for any errors? I'd hazard a guess that you've not changed the wsProxyURL from localhost to the address where wsProxy is hosted: https://github.com/stuicey/SSHy/blob/master/index.html#L9...

Is the websocket proxy available from the machine you're connecting from? The connection timing out would suggest theres no route available or its getting dropped by a firewall rule.

Might be a copy paste mistake while making this ticket but looks like you're trying to use a private key as a certificate? If you were this error makes sense...

Apologies missed this notification... Whats the output you get in the wsproxy window when the connection fails? I'd guess its a certificate related issue, either something with the chain or...