-
Notifications
You must be signed in to change notification settings - Fork 743
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
Cannot connect to host #1042
Comments
And this happens from the Chrome app: Server fingerprint unknown. Store and continue? (Yes/No): yes
|
Now I am trying mosh installed in Ubuntu, but the following error shows up:
|
|
Hi there. The first errors you were showing looked like ssh-connection issues. Did you get those sorted out? The last error you showed was about the need for a UTF-8 locale. Did you generated a UTF-8 locale on both your client and server machines? |
No reply, so closing for now. Please leave a comment here (or open a new issue) if you're still having problems. |
I think this will help with the papercut of "Did not find mosh server startup message". This message confuses people; often the real problem is that the command to start the remote mosh-server failed somehow. Fixes mobile-shell#1042, partially resolves mobile-shell#1005. Also relevant for mobile-shell#1042 and countless questions on IRC.
I think this will help with the papercut of "Did not find mosh server startup message". This message confuses people; often the real problem is that the command to start the remote mosh-server failed somehow. Fixes mobile-shell#1042, partially resolves mobile-shell#1005. Also relevant for mobile-shell#1042 and countless questions on IRC.
I think this will help with the papercut of "Did not find mosh server startup message". This message confuses people; often the real problem is that the command to start the remote mosh-server failed somehow. Fixes mobile-shell#1042, partially resolves mobile-shell#1005. Also relevant for mobile-shell#1042 and countless questions on IRC.
I think this will help with the papercut of "Did not find mosh server startup message". This message confuses people; often the real problem is that the command to start the remote mosh-server failed somehow. Fixes mobile-shell#1042, partially resolves mobile-shell#1005. Also relevant for mobile-shell#1042 and countless questions on IRC.
I have mosh installed in the server and client, I type mosh -p xxxx user@xxx.xxx.xx.xx but following error shows up:
usr/local/bin/mosh: Could not connect to 210.16.120.32, last tried 210.16.120.32: IO::Socket::INET: connect: Connection refused ssh_exchange_identification: Connection closed by remote host /usr/local/bin/mosh: Did not find remote IP address (is SSH ProxyCommand disabled?).
server in centOS 7.0 and connecting from osx Mojave
The text was updated successfully, but these errors were encountered: