Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error handling #39

Open
candlerb opened this issue Sep 18, 2020 · 0 comments
Open

Better error handling #39

candlerb opened this issue Sep 18, 2020 · 0 comments

Comments

@candlerb
Copy link

I am using SSHy with Chrome 85.

When something goes wrong, error handling isn't great. In some cases, all I see is the "spinner" spinning (or in the case of wrapper.html, just a black screen), and no other error displayed.

Here are some ways to replicate this:

  • Simply don't start wsproxy. tcpdump on port 5999 shows a SYN and RST exchange. SSHy shows nothing, and the spinner just keeps going.
  • Run the stock version of wsproxy, instead of the stuicey one. tcpdump shows the exchange getting as far as SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, at which point it hangs with the spinner spinning.

Another minor bug:

  • Connect with a wrong password. SSHy correctly says "Invalid Username or Password" in the dialog box. But if you then enter the correct password and hit enter again, the terminal displays WebSocket connection failed: Error in connection establishment: code 1005. You have to refresh the screen and enter the target, username and (correct) password again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant