≡ Menu

OS X Terminal: -bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory Fix

I'm a new Apple OS X Mabbook user. I am getting an error which read as follows when I connect to any remote Linux/Unix/BSD server or machine through OS X ssh Terminal app:

ssh user@server1.cyberciti.biz
Last login: Wed Mar 26 08:45:36 2014 from
-bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory

How do I fix this error?

Tutorial details
DifficultyEasy (rss)
Root privilegesNo
Estimated completion time2m
This warning or error is part of both OpenSSH server and OS X ssh terminal client issue. It can be fixed using various methods.

Understanding LC_* environment variables

Type the following command on remote server to display of all locales supported by Glibc:

$ locale -a

Next, type the following command to display settings on your local system (OSX/Unix/Linux based desktop):

echo "$LC_CTYPE"

Sample outputs:


The above commands display the country and language names, the character encoding used by the locale. Your local ssh client is sending your LC_* environment variables to remote sshd server. In other words, SSH will try to set every LC_* variable you have set on your local OSX system on the remove server too. Here is an example of such problem:

Fig 01: warning setlocale lc_ctype cannot change locale (utf-8)

Fig 01: warning setlocale lc_ctype cannot change locale (utf-8)

Fixing the LC_CTYPE: cannot change locale (UTF-8) error on Linux/OS X

This can be fixed as follows.

Method #1: If you are using the Terminal app on OS X

If you are using the 'Terminal' app then click on

Terminal > Preferences > Select Terminal type such as Basic (default) > Advanced tab

Make sure that the 'Set locale environment variables on startup' is unchecked as follows:

Fig.02: Fixing OS X terminal by unsetting ''Set locale environment variables on startup' check box

Fig.02: Fixing OS X terminal by unsetting ''Set locale environment variables on startup' check box

You must close all ssh session and relaunch Terminal app.

Method #2: Preventing OpenSSH Client from sending the LC_* variables on OS X / Linux / Unix desktop

Edit /etc/ssh/ssh_config or /etc/ssh_config file, enter:

$ sudo vi ~/.ssh/config

Remove or comment out as follows:

#SendEnv LANG LC_*

Save and close the file.

Option #3: Install required locale on the remote server

Finally, you can fix this problem either installing the desired locale using the localedef command, or consider choosing a different locale in locale/remote system:

# localedef -i en_US -f UTF-8 en_US.UTF-8
Tweet itFacebook itGoogle+ itPDF itFound an error/typo on this page?

{ 16 comments… add one }

  • Mark May 3, 2014, 7:20 pm

    Thank you very much, Nix! This solves my problem! :)

  • Atif May 24, 2014, 7:56 am


    The /etc/ssh_cofig change worked for me too.

    • Gustavo July 11, 2014, 5:13 pm


    • Leonardo September 7, 2014, 6:58 pm

      Thank you! This was the unique method that worked for me. (I’m using os x mavericks)

  • Devashish August 13, 2014, 7:20 am

    The /etc/ssh_cofig fix worked for me. Thanks!
    It was quick, nice, and easy change.

    In your post, You should change
    sudo vi ~/.ssh/config
    sudo vi /etc/ssh_cofig


  • ohad September 1, 2014, 10:00 am

    Thanks that worked like a charm(Method #1)

  • Ramon November 18, 2014, 5:40 pm

    Thanks a lot!! (solved with method #1)

  • Andrey January 8, 2015, 11:16 am

    Thanks a lot!

  • Zague58 April 12, 2015, 1:07 am

    Funcionó con localedef -i en_US -f UTF-8 en_US.UTF-8, ya no se presenta el problema.

  • MacHamster May 3, 2015, 9:25 am

    Just wanted to say thanks.
    Using iTerm2 – but there’s no option to unset locale variable on startup in the GUI, so the /etc/ssh_config edit was the way to go – and worked.

    • Keijro August 6, 2015, 6:14 am

      In iTerm2 it is done under Preferences -> Profiles -> Terminal
      Uncheck the box “Set locale variables automatically”

  • Mosh May 27, 2015, 1:40 am

    It works!
    Thank you.

  • kde35 July 26, 2015, 7:54 am

    Hi, when I tried the third method, I get the error
    “Can’t open charmap file UTF-8: No such file or directory”. Any idea on how to fix this?

  • bs July 29, 2015, 5:47 pm


  • dangors August 12, 2015, 10:58 am

    Hi thanks very much
    Method #2 worked for me but
    i did
    nano /etc/ssh_config to
    fix my error ; now i don’t have the problem again when i ssh into my remote machine.

  • Omer September 14, 2015, 11:43 am

    option 3 worked. Thanks

Leave a Comment