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.

Sign up for GitHub

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

Jump to bottom

Cannot connect to host #1042

Closed
gitgitgat-zz opened this issue May 31, 2019 · 5 comments · May be fixed by #1232
Closed

Cannot connect to host #1042

gitgitgat-zz opened this issue May 31, 2019 · 5 comments · May be fixed by #1232
Labels
support

Comments

@gitgitgat-zz
Copy link

gitgitgat-zz commented May 31, 2019 •
edited

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
@gitgitgat-zz
Copy link
Author

And this happens from the Chrome app:

Server fingerprint unknown. Store and continue? (Yes/No): yes
Authentication types supported by server:

  • Public Key
Trying authentication type Public Key
No ssh key found.
ssh authentication failed: Access denied. Authentication that can continue: publickey,gssapi-keyex,gssapi-with-mic

SSH Login failed.

ssh user@xxx.xxx.xx.xx has no problems connecting.

@gitgitgat-zz
Copy link
Author

gitgitgat-zz commented Jun 1, 2019 •
edited

Now I am trying mosh installed in Ubuntu, but the following error shows up:
and that is using the mosh-server option

The locale requested by LC_CTYPE=UTF-8 isn't available here.
Running `locale-gen UTF-8' may be necessary.

mosh-server needs a UTF-8 native locale to run.

Unfortunately, the local environment ([no charset variables]) specifies
the character set "US-ASCII",

The client-supplied environment (LC_CTYPE=UTF-8) specifies
the character set "US-ASCII".

locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=
LANGUAGE=
LC_CTYPE=UTF-8
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
Connection to xxx.xxx.xx.xx closed.
/usr/local/bin/mosh: Did not find mosh server startup message. (Have you installed mosh on your server?)

@gitgitgat-zz
Copy link
Author

gitgitgat-zz commented Jun 8, 2019 •
edited

export LC_ALL="en_US.UTF-8" has been working for that

@eminence
Copy link
Member

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?

@eminence
Copy link
Member

No reply, so closing for now. Please leave a comment here (or open a new issue) if you're still having problems.

cgull added a commit to cgull/mosh that referenced this issue May 17, 2020
@cgull
mosh.pl: Report errors on server command failure.
185881b 
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.
cgull added a commit to cgull/mosh that referenced this issue May 18, 2020
@cgull
mosh.pl: Report errors on server command failure.
00b3688 
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.
cgull added a commit to cgull/mosh that referenced this issue May 31, 2020
@cgull
mosh.pl: Report errors on server command failure.
5435f7d 
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.
cgull added a commit to cgull/mosh that referenced this issue Oct 27, 2022
@cgull
mosh.pl: Report errors on server command failure.
fc1693f 
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.
@cgull cgull mentioned this issue Oct 27, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
support
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Report errors from mosh-server startup to the user cgull/mosh
2 participants
@eminence @gitgitgat-zz