UBUNTU MOSH SERVER INSTALL
UBUNTU MOSH SERVER CODE

Just like declaring overriding LANG/LC_* variables in. Generating en_UA.UTF-8 locale definitions on all the servers I am connecting to is out of question too. I could generate en_UA.UTF-8 locale definition locally, and that would make terminals define correctly LC_* variables, but they will send them over to the servers I am connecting to, and there mosh-server (and probably some other commands) will fail. When I was connecting from Terminal, the locale was set to C which is not UTF-8, as I mentioned above when I was connecting from iTerm2, the locale was defaulted to UTF-8 and this also irked mosh-server because there was no definition for it in the system. This makes the remote side of the connection declare them, and then mosh-server refuses to start because it requires a UTF-8 native locale to run. $ grep -n -B1 SendEnv /etc/ssh/ssh_config

How does this affect the remote side of mosh connection – the server I am connecting to, though? Well, ssh – and mosh uses it for authentication phase – by default forwards the LANG and LC_* environment variables to the remote server it is connecting to:

UBUNTU MOSH SERVER CODE

In my situation, the country was Ukraine with the country code UA, and of course there is no en_UA locale. I googled a bit the mosh error message but didn’t find anything illuminating then I noticed that when I was connecting to the server with ssh, iTerm2 would emit the following error message:Įn_AU.ISO8859-15 en_GB.ISO8859-1 en_NZ.US-ASCIIĮn_AU.US-ASCII en_GB.ISO8859-15 en_NZ.UTF-8Įn_CA.ISO8859-15 en_IE.UTF-8 en_US.US-ASCIIĪha, not that many countries are supported, just the Five Eyes and Ireland! That explains why that person from South Africa ran into this issue with en_ZA and iTerm2: every combination of English as the OS language with an odd country will result in it. This actually only increased my curiosity: a freshly installed MacOS with still almost default configuration was causing mosh to fail on connection over locale settings. Here I realized I have recently done a complete clean re-install and never restored whatever locale settings I had in my. (Have you installed mosh on your server? )Īpparently, something was wrong my with locale. usr/local/bin/mosh: Did not find mosh server startup message. Locale: Cannot set LC_ALL to default locale: No such file or directory The client-supplied environment (LC_CTYPE =UTF-8 ) specifies Unfortunately, the local environment (LC_CTYPE =UTF-8 ) specifies Running `locale-gen UTF-8' may be necessary. The locale requested by LC_CTYPE =UTF-8 isn 't available here. etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8 ): No such file or directory To my surprise, mosh failed to connect with the following error message: This weekend I was doing an initial configuration to a new server I provisioned from OVH hosting.

UBUNTU MOSH SERVER INSTALL

It’s one of the first tools I install on a new server and from then on I switch from ssh to mosh. I am quite a user of mosh – a mobile shell that makes it really convenient to work via ssh over unstable Internet connection or when roaming across different wifi networks. export LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 Solution: If you are not in US/GB/CA/IE/AU/NZ, add the following line to your. OR when connecting with ssh from iTerm2 you get the error message -bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory Locale: Cannot set LC_CTYPE to default locale: No such file or directory The locale requested by LC_CTYPE=UTF-8 isn't available here. Mosh-server needs a UTF-8 native locale to run. Problem: trying to connect to a remote server with mosh you see error messages like: mosh-client needs a UTF-8 native locale to run.

Ubuntu mosh server