I have the following alias on my local machine: alias gom='mosh -- user@host "/path/to/specific/zsh"' I use it to connect to a remote machine with an interactive shell. I would like to **modify this alias** to run a specific function my_func defined in .zshenv **in the remote machine** as soon as I log in on it (when using this alias). How can I do so? I have tried the following: * alias gom='mosh -- user@host "/path/to/specific/zsh"; my_func;' * alias gom='mosh -- user@host "/path/to/specific/zsh; my_func"' * alias gom='mosh -- user@host "/path/to/specific/zsh & my_func"' Some of the above solutions disconnect me from the remote sessions, while others don't, but none of them work.

When connecting to my development server via ssh, I can forward remote ports to local ports via: ssh my-user@example.com -L 5432:localhost:5432 However I'd rather use mosh because my connection tends to drop. I tried extending my usual mosh command (that works) with the --ssh parameter: mosh --ssh "ssh -L 5432:localhost:5432" my-user@example.com Which gets me connected without error - but doesn't do anything for my ports. **Is there a way to make port forwarding work when connecting via mosh?**

I am trying to connect from my Gentoo to RHEL server. Both have mosh installed, however I get this error: petanb@localhost ~/Documents $ mosh root@server 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 ([no charset variables]) specifies the character set "US-ASCII". LANG= LC_CTYPE="POSIX" 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 server closed. /usr/bin/mosh: Did not find mosh server startup message. On RHEL I have following locales: # locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= How can I fix this? UPDATE: The problem seem to be on Gentoo side, connecting to debian server produces same error, connecting using other distros works. UPDATE2: I fixed it by adding LANG="en_US.UTF-8" export LANG into ~/.bashrc

The following steam of error messages are being generated when trying to connect to a server via mosh. This is notwithstanding the fact that the command was previously run and showed mosh was already installed on the server.

sudo apt-get install mosh
[sudo] password for jerdvo:
Reading package lists... Done
Building dependency tree
Reading state information... Done
mosh is already the newest version (1.3.2-2.1build3).
The following package was automatically installed and is no longer required:
  libfwupdplugin1
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 46 not upgraded.

The errors are as follows. There is an indication of inappropriate locales in addition to Did not find mosh server startup message Which rabbit should I pursue first and how? server: ubuntu 20.04 local: OSX 10.13.6

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

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 (LC_CTYPE=UTF-8) 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 159...33 closed.
/usr/local/bin/mosh: Did not find mosh server startup message. (Have you installed mosh on your server?)

I've tried this, as suggested in the comments: locale-gen UTF-8 Error: 'UTF-8' is not a supported language or locale ... which I do find odd... Then ran sudo dpkg-reconfigure locales en_us.UTF-8 sudo update-locale LANG=en_US.UTF-8 Error: 'UTF-8' is not a supported language or locale Where now?

I have a reverse SSH tunnel setup between bigbox and jump so that I can login into bigbox from where ever (it is behind a firewall) by using jump as a middle man. This works fine: I just ssh bigbox from my laptop and presto, I am in. Now, I want to use mosh to reduce lag, but I am not sure how to get it working. I have no experience with Mosh from earlier. I basically want to use SSH to setup the initial connection using my configuration and then leave it to Mosh. Unsurprisingly, neither doing mosh bigbox nor mosh --ssh="ssh bigbox" localhost did work:

$ mosh bigbox
/opt/homebrew/bin/mosh: Could not connect to localhost, last tried ::1: Connection refused
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535
/opt/homebrew/bin/mosh: Did not find remote IP address (is SSH ProxyCommand disabled?).

Here is my config: # ~/.ssh/config

Host jump
    HostName jump.somedomain.com
    User jumpuser

# https://unix.stackexchange.com/questions/693885/hardening-reverse-ssh-tunnel-via-jump-host/693886#693886 
Host bigbox
    ProxyJump jump
    User my_user

    # Using a reversed SSH tunnel
    HostName localhost
    Port 20001

The simplest program that should draw a horizontal line: int main() { initscr(); for (int i=0;i<10;i++) addch(ACS_HLINE); getch(); endwin(); } works ok localy, but over MOSH connection result is qqqqqqqqqq. I tested other well known ncurses programs this way (over MOSH connection) and some of them works well, like: alsamixer, vim, tmux... but other tested also showed "ugly characters", like: tetris game (bastet), dialog (showing dialogs from shell scripts). So the problem again for myprogram above, tetris, dialog and others is: - it works localy in xterm and virtual-terminals(term=linux) and tmux/screen. - it works well over SSH too. - it shows q and x characters instead of lines over MOSH client Mosh is very usefull program that resolves ssh disconnections on laptop wifi. It creates its own terminal and sets TERM variable to xterm. Right before starting program over mosh, TERM var is 'xterm', locale command shows LANG=en_US.UTF8,LC_ALL="", fonts seems ok (and same results with testing different fonts) Does someone know how to solve or further debug this problem? Simplest simulation: sudo apt-get install mosh bastet #<--install mosh and tetris bastet #<--tetris works ok mosh -- 127.0.0.1 bastet #<--q and x chars instead of lines

Reading this Q&A on the site: Can I re-attach to a mosh session? made me wonder about the use cases for mosh. Say I start tmux on my local client, and then mosh to a remote host from within tmux. From this mosh session, I start a long process on the remote machine that e.g. prints info over time to stdout. Say that I then lose connectivity on my client, or that I restart my local client (for whatever reason). Will I be able to (1) re-attach to my local tmux session, (2) **still** see my mosh connection alive, and (3) still the server process running and displaying its output in it?

I've just started using mosh and I'm left thinking to myself "why didn't I start using this like two years ago?" I'm even more impressed by the fact that it reads my ~/.ssh/config and respects the aliases in it. The only thing I'd like now is for tab completion on the aliases, like ssh does. Is there a way?

I have a RPi running ArchLinux where I can login with mosh when ufw is disabled, but it doesn't work when it's enabled. This is my ufw setup: ❯ sudo ufw status numbered Status: active To Action From -- ------ ---- [ 1] 22/tcp ALLOW IN Anywhere [ 2] 60001/udp ALLOW IN Anywhere I've checked with wireshark on PC side (also running ArchLinux) that when ufw is disabled, 22 and 60001 are the sole ports being used. When I enable ufw I just keep getting TCP retransmissions on port 22. I also tried ufw limit ssh/tcp and ufw allow mosh: ❯ sudo ufw status numbered Status: active To Action From -- ------ ---- [ 1] 22/tcp LIMIT IN Anywhere [ 2] mosh ALLOW IN Anywhere [ 3] 22/tcp (v6) LIMIT IN Anywhere (v6) [ 4] mosh (v6) ALLOW IN Anywhere (v6) Any idea of what's left to fix this?

I am using mosh for my regular terminal based activities. However I have also remote file sever access (via sftp) in nautilus. (I am using Ubuntu 16.10 with unity). (In nautilus, in the URL bar, I just type: sftp://user:password@host:port/dir/to/enter And then the entire (remote) filesystem is mounted...) Is there anyway, I can mount this remote FS using mosh? A (possibly similar) question gives a negative answer, however this is 2015 question and I am sure mosh has come a long way after that. -- Mike

Is there a way to use [mosh](http://ports.su/net/mosh) without giving up the local scrollback? Basically, in some circumstances, IP-roaming is indeed useful and needed, but the extra terminal emulation and key prediction seems to only be getting rid of the local scrollback buffer lines and the session history.

I am trying to figure out a way to detect whether the current terminal/connection (and under a tmux session as well) is through **mosh** or not. From [this thread](https://unix.stackexchange.com/questions/235485/how-do-i-know-which-mosh-client-i-am) , I found which pseudo-terminal session I am currently on: $ tty /dev/pts/69 So, I need to some information of the process that spawned this pseudo-terminal, or owns this tty as a children. With the information, perhaps I might be able to determine whether it is from sshd or mosh. But how can I do that? *Another challenge*: If the current shell is **under tmux**, the retrieved tty might not match the sshd/mosh-server information since tmux also allocates another pseudo-terminal. Regardless of how the tmux session was created, I'll need to distinguish my current connection is from SSH or mosh. How will it be possible? ### Some trials: (1) For SSH, it was possible to find the sshd process that matches the tty: $ ps x | grep sshd | grep 'pts\/27' 5270 ? S 0:00 sshd: wookayin@pts/27 So I can know the current connection is through SSH. However, through mosh, I could not find any relevant information. (2) Using environment variables like SSH_CLIENT or SSH_TTY might not work because both ssh/mosh set these variables, and it is even wrong inside a tmux session.

[The mobile shell](https://mosh.mit.edu/) claims many benefits, especially with mobile connections. Many mobile plan prices scale with the amount of data transferred. So I wonder whether I can use Mosh to cut down in data usage. [A tutorial on DigitalOcean](https://www.digitalocean.com/community/tutorials/how-to-install-and-use-mosh-on-a-vps) states that > Mosh [...] will only communicate changes to the currently visible screen area. This allows it to radically reduce the bandwidth [...] But does not give any statistics on how much bandwidth is gained and whether this really weighs out the additional overhead of establishing and maintaining a connection via UDP. Are there any tests, experiences that compare SSH to Mosh in real-world-scenarios, especially - used with _screen_ or _tmux_, - on a mobile connection while moving between different connection modes or cell towers, - for long-lived sessions?

I knew this app in another question on Unix SE. And it says: > Change IP. Stay connected. > > Mosh automatically roams as you move between Internet connections. Use > Wi-Fi on the train, Ethernet in a hotel, and LTE on a beach: you'll > stay logged in. Most network programs lose their connections after > roaming, including SSH and Web apps like Gmail. Mosh is different. How could that possible? Is that a simple reconnect technology?

I have installed mosh on my MacOS via brew. Everything went perfect. After I tried to connect to my server, I got a message: localhost:~ darkstaff$ mosh root@*.*.*.* root@*.*.*.*'s password: bash: mosh-server: command not found Connection to *.*.*.* closed. /usr/local/bin/mosh: Did not find mosh server startup message. (Have you installed mosh on your server?) Do I have to install Mosh on my server? If so, how could I install? I am using Debian.

I've set up the .zshrc of my user account on all of the hosts to which I connect to automatically start tmux on login as long as it's not already running.

[ -z "$TMUX" ]; then
   tmux attach -d || tmux new
fi

This works well until I ssh (or mosh) into my own account on a remote host from within a tmux session on the local host. Since the $TMUX macro isn't passed from the local host to the remote, tmux launches on the remote host and I now have two nested tmux sessions. Is there a way to avoid this while keeping the auto-launching behaviour? Ideally I'd like the remote shell to know that it's being launched from within a tmux session on the host that is connecting and to not launch a second tmux instance. I've already tried checking $TERM in the remote shell but it is always xterm-256color regardless of whether it is running within a tmux session on the local machine.

I have a few services (such as syncthing) set up as user-level systemd services on my Arch machine. They work great when I ssh in, but when I connect using mosh, they seem to start and then immediately stop again. For instance, I can connect with mosh, and do systemctl --user status syncthing and get back that it's running or shutting down; then, repeating the command, I get Failed to connect to bus: No such file or directory Based on other similar questions, I've checked that $XDG_RUNTIME_DIR is set within the mosh session: $ echo $XDG_RUNTIME_DIR /run/user/1000 Indeed, it seems the user manager shuts down cleanly, even though I'm still connected to the session: $ systemctl status user@1000.service ● user@1000.service - User Manager for UID 1000 Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor preset: disabled) Active: inactive (dead) [...] Aug 16 18:36:56 ip-172-70-3-138 systemd: Closed GnuPG cryptographic agent and passphrase cache (restricted). Aug 16 18:36:56 ip-172-70-3-138 systemd: Reached target Shutdown. Aug 16 18:36:56 ip-172-70-3-138 systemd: Starting Exit the Session... Aug 16 18:36:56 ip-172-70-3-138 systemd: Received SIGRTMIN+24 from PID 7877 (kill). Aug 16 18:36:56 ip-172-70-3-138 systemd: Stopped User Manager for UID 1000. How do I keep the services alive? --- **Update:** Tmux sessions themselves don't start or keep systemd services alive, at least on my system. I haven't been able to find out whether that's correct behavior or not, but it seems to me a tmux session should keep systemd from closing things down. Consider the case where I'm editing a file using emacsclient: I would expect that if my connection dropped for a minute, whether using mosh or tmux, the emacs daemon would stay alive.

Ever since I've started using [mosh](http://ports.su/net/mosh) , I'm getting way too many entries in my /var/log/wtmp file of [last(1)](http://mdoc.su/o/last.1) on a Linux box. cnst pts/8 172.56.2x.yz via Mon May 19 08:19 still logged in cnst pts/8 mosh Mon May 19 08:19 - 08:19 (00:00) cnst pts/8 172.56.2x.yz via Mon May 19 08:18 - 08:19 (00:01) cnst pts/8 mosh Mon May 19 08:18 - 08:18 (00:00) cnst pts/8 172.56.2x.yz via Mon May 19 08:18 - 08:18 (00:00) cnst pts/8 mosh Mon May 19 08:18 - 08:18 (00:00) cnst pts/8 172.56.2x.yz via Sun May 18 20:11 - 08:18 (12:06) cnst pts/8 mosh Sun May 18 20:11 - 20:11 (00:00) cnst pts/8 172.56.2x.yz via Sun May 18 20:11 - 20:11 (00:00) cnst pts/8 mosh Sun May 18 20:10 - 20:11 (00:00) cnst pts/8 172.56.2x.yz via Sun May 18 19:55 - 20:10 (00:15) cnst pts/8 mosh Sun May 18 19:55 - 19:55 (00:00) cnst pts/8 172.56.2x.yz via Sun May 18 19:55 - 19:55 (00:00) cnst pts/8 mosh Sun May 18 19:55 - 19:55 (00:00) cnst pts/8 172.56.2x.yz via Sun May 18 19:24 - 19:55 (00:30) cnst pts/8 mosh Sun May 18 19:24 - 19:24 (00:00) cnst pts/8 172.56.2x.yz via Sun May 18 19:24 - 19:24 (00:00) cnst pts/8 mosh Sun May 18 19:23 - 19:24 (00:00) What's up with those 00 hours, 00 minutes, login entries? Any way to adjust the parameters of mosh to not be so strict about reporting the very brief periods in the loss of connectivity? Not really interested in having a couple of seconds of connectivity issues reported so loudly.

I've installed mosh on my laptop using Macports and on my FreeBSD server using ports. Whenever I try to connect to my server I get the following error:

Password for xxxxxx@xxx.xxx.xx.xx:
zsh:1: command not found: mosh-server
Connection to xxx.xxx.xx.xx closed.
/opt/local/bin/mosh: Did not find mosh server startup message.

I can't find any binaries on my BSD box called mosh-server with whereis.

I work with a very large remote filesystem, so I like to use mosh instead of ssh for low-connectivity persistent connections, or just when my computer sleeps. For editing files though, I mount the remote filesystem with SSHFS so I can use my computer's native GUI editor. mosh is a great alternative to ssh to create persistence, but is there a similar thing for SSHFS or remote filesystem mounting?