Stuck on connecting...

[dinosmm]

Hi there,
Thank you for creating this.
I have installed it on a VPS to use for a class project. I can access the login page, but any server I try to connect to, it keeps 'connecting...' forever.
Do I need to open any incoming ports in my firewall, or is there something else I've not done right?
I am not using a websocket as I didn't think it would be necessary, this will be very low traffic.

EDIT: I have just installed wsProxy and it's running, but I still get stucj on 'connecting...'

[stuicey]

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 . Note; this is in relation to your local web browser.

[Relix360]

Hey, im also stuck there

(index):222 WebSocket connection to 'ws://192.168.3.143:5999/' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT startSSHy @ (index):222 onclick @ (index):464 (anonymous) @ (index):55 combinedLibs.comb.js:338 Uncaught TypeError: Cannot read property 'auth' of undefined at m (combinedLibs.comb.js:338) at d.a.fit (combinedLibs.comb.js:338) at termInit ((index):285) at WebSocket.ws.onclose ((index):257) m @ combinedLibs.comb.js:338 a.fit @ combinedLibs.comb.js:338 termInit @ (index):285 ws.onclose @ (index):257

[stuicey]

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.

[candlerb]

@dinosmm:

EDIT: I have just installed wsProxy and it's running, but I still get stucj on 'connecting...'

Which version of wsProxy? I found that the one from npm repositories (npm i -g wsproxy) didn't work. Looking at tcpdump, the exchange got as far as

SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

and then hung. After uninstalling this, and installing the one which is a git submodule of the SSHy repository, it worked. Instructions are here.

I think it would be helpful though if on error conditions, SSHy could display a message and stop the spinner. Otherwise it just looks like it has hung.

Aside: I couldn't get SSHy to work with websockify. SSHy asks for the "base64" websockets protocol, while websockify now only implements the "binary" websockets protocol.