-
Notifications
You must be signed in to change notification settings - Fork 727
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
/usr/local/bin/mosh: Did not find mosh server startup message. #102
Comments
Wow. I feel like an idiot. I forgot to install mosh-server on the host. Sorry. |
I also have this issue, but unlike you I have mosh is installed on the both server and client. en_US.UTF-8 on Ubuntu oneiric server edn. and installed via Homebrew on Mac on client side. |
Same problem here. Mac<->Mac. |
@zcode Possibly related to env transfer. Mac sends
|
The problem is that export PATH=/usr/local/bin:$PATH |
Sorry to resurrect a dead item, but @edw was correct for me and I'm wondering if there is a need to report to the mosh invoker the true error instead of the symptom. Using |
I had the same problem and what @nkuln said fixed it for me. |
@edw was correct for me as well. You can confirm if this is your issue with: $ ssh your-host.dev /usr/bin/which mosh-server
# nothing
$ ssh your-host.dev echo \$PATH
/usr/bin:/bin:/usr/sbin:/sbin Also relevant In OSX Yosemite, why can I set many environment variables for GUI apps, but cannot set the specific variable PATH. Previously you could set Lastly, a plug for |
I still have this error and advice of @edv didn't work for me |
@edw's solution worked for me, Linux -> Mac via homebrew |
yap, same problem here (OSX<->OSX), homebrew installation won't find mosh-server path via ssh. Two ways to solve this:
|
Following up on rubendepredro's solution. Since I installed mosh using MacPorts (on both ends), invoking mosh using "--server=/opt/local/bin/mosh-server" totally does the trick for me. |
I'm confused. While this solution works, I did not expect the following:
So… ssh finds EDIT: |
@jemus42 When you ran |
Well, that's embarrassing. Thanks for clearing that up m) |
I think this is an ordinary issue for many users, getting start document is too simple. |
I have the same problem as shown by @toolbear
I have tried adding Does anyone know what else I could try/ debug? |
@tnguyen14, If you can execute |
@edw it is that path :; which mosh-server
/usr/local/bin/mosh-server |
@tnguyen14 did mosh --server=/usr/local/bin/mosh-server not work in your case? |
@carloscabanero it does. But I don't wanna type the whole thing every time I need to log into the server. If there's a more permanent solution, it'd be great. |
@tnguyen14, is it in |
@edw good clarification. it is on the destination server machine I'm moshing to. |
@tnguyen14, dumb question: is |
@edw yes default shell is
|
@tnguyen14, I am completely baffled. I, for what it's worth cannot connect to my own MacBook without specifying a |
@edw yeah this is me trying to connect to an iMac. SSH works fine. Mosh connecting to a linux box also works fine. |
If @tnguyen14 sets (I used to believe |
Also, adding |
@cgull I'm adding it to |
For zsh (installed using Homebrew) the path can be set in |
from the docs: "Behind the scenes, the mosh wrapper script will SSH to the server, start up mosh-server, and then close the SSH connection" it is easy to think the wrapper script will transfer mosh-server to the target before running it. the documentation NOWHERE says I have to install mosh-server on the target. in fact, it would be a much better product if it would just install itself at the target without my having to do it |
Thanks for this feedback. Our website is pretty clear (The first bit of text under "Getting Mosh" is "The Mosh package should be installed on both the client and server. Please find your platform below for installation instructions."), but we'll happily take a pull request to the mobile-shell/moshweb repo if you have a suggestion. We've considered the idea of trying to have mosh automatically install itself on the server (a server whose architecture might be different than the client!), but the complexity of trying to do this reliably for any pair of architectures, and the fact that no other program works like this, has weighed against. You have to install sshd on the server to use SSH; you have to install mosh-server on the server to use Mosh. |
Does anyone know why I might have the issue I'm seeing, where I have to specify the path to |
I think because the |
@javabrett No, the @tnguyen14 See what you get from these commands:
|
|
@tnguyen14 Well, now you see what the problem is and you can debug it without the involvement of Mosh. Once you can make the (It sounds like your server is one of the systems where |
I figured out what was wrong with my setup. I had this in my [[ -z $PS1 ]] && return Instead, I modified it: [[ -z $PS1 ]] && export PATH="$PATH:/usr/local/bin" && return and that fixed my issue. |
I needed to run sudo locale-gen en_US.UTF-8 on the server |
On two Macs, one is okey and another one doesn't work. Solved by
and change the
|
Nothing worked for me but this surely did, please check this answer: https://askubuntu.com/a/229512 I added these 2 lines to
|
|
In case someone stumbles on this as I did and none of the fixes work: the ssh-add <your private key file path> and then log in without the -i flag mosh name@host |
FWIW - none of the suggestions here worked for me. I eventually discovered that the server-side was running dropbear (on a Raspberry Pi). Switching to openssh-server resolved the issue. |
The issue with dropbear is discussed in #819. Since the original issue was filed (and resolved) 8 years ago, I'm locking this issue. If anyone else is having problems with mosh, please open a new issue so that we can discuss the specifics of your environment/problem. Thanks! |
I installed via Homebrew, but I can't seem to log into any servers.
$ mosh user@host (user and host are different)
user@host's password: (i entered the correct password)
bash: mosh-server: command not found
Connection to host closed
/usr/local/bin/mosh: Did not find mosh server startup message.
Any help would be appreciated. Thanks! :-)
The text was updated successfully, but these errors were encountered: