Directory/filenames which contain non-English/Asian characters show up as ?????? or are corrupt

If you’re having trouble with your filenames or content not showing up correctly, you can activate UTF support by adding the following to your.bash profile file. For instructions on how to update the file (depending on whether you’re using an FTP client or SSH), see the following articles:

Using FTP to create and edit a file
Using SSH export to create and edit a file LC ALL=en US. UTF-8 \sexport LANG=en US. UTF-8 \sexport LANGUAGE=en US. UTF-8 \sexport G FILENAME ENCODING=UTF-8 UTF-8 is almost certainly already enabled. You may check this in your terminal by typing ‘locale’:

[server]

LANG=en US LANG=en US LANG=en US LANG=en US L

LC CTYPE=”UTF-8 LANGUAGE=”UTF-8 LANGUAGE=”UTF-8 LANGUAGE=”UTF-8 LANGU “n United States

UTF-8″ \sLC NUMERIC=”en US.

LC TIME=”en US” UTF-8″

UTF-8″ \sLC COLLATE=C \sLC MONETARY=”en US.

UTF-8″ \sLC MESSAGES=”en US.

UTF-8″ \sLC PAPER=”en US.

LC NAME=”en US” UTF-8″

UTF-8″ \sLC ADDRESS=”en US.

LC TELEPHONE=”en US” UTF-8″

UTF-8″ \sLC MEASUREMENT=”en US.

UTF-8″ \sLC IDENTIFICATION=”en US.

UTF-8 is a Unicode character set “ALL=LC ALL
The first line is LANG=en US, as you can see.
UTF-8. If this still doesn’t work, the issue is most likely with the terminal client you’re using. In PuTTY, you can change the translation option to UTF-8 manually.

Follow these procedures to change the translation option:

Open the PuTTY configuration window.
trans.fw.png 06 charset
Select Window > Translation from the Category list on the left.
Select UTF-8 from the Remote character set selection.
Return to the ‘Session’ category and save your current session, including all settings.
When you use PuTTY to log in again, the non-English characters appear appropriately.

Idle connections are dropping

GreggHost and other ISPs may terminate ssh connections that have been idle for more than a set amount of time. You can change this parameter in PuTTY (for Windows) in the Configuration box:

Open the PuTTY configuration window.
Select Connection from the Category list on the left.
Enter 15 in the field ‘Seconds between keepalives (0 to turn off).’
‘Enable TCP keepalives (SO KEEPALIVE option)’ should be checked.
connection.fw.png (#7)
Every 15 seconds, the SSH client queries the server for a sign of life, keeping the connection open.

Connection issues

When connecting, you may encounter the following error:

There are no authentication methods that are supported (server sent public key)

It’s possible that there’s a problem with the way the public key was saved. PuttyGen will generate the following public key file:

—— START WITH THE SSH2 PUBLIC KEY ——
tr7mmimiTjkoSCrJh1kqalPSpi8rglT/Bp67Ql2SZwvUFfMzHI AAAAB3NzaC1yc2CAAAABJQAAAIEAhGF6GIuMY8FJ1+CNApnSY1N2YSlkYz72Yvwu a6N1nFpBklz1+dsIMg4rc
SSH2 PUBLIC KEY —— END SSH2 PUBLIC KEY ——
On a single line, the key must be saved. Open the key in PuttyGen, copy it, and paste it into a text editor such as notepad. As a result, the key is preserved on a single line:

ssh-rsa CNApnSY1N2YSlkYz72Yvwua6N1nFpBklz1+dsIMg4rcTLcF34M/tW5Yz+NUDAw2AEbxQ32FPgw7sAOIXktkYOHtr7mmimiTjkoSCrJh1kqalPSpi8rglT/Bp67Ql2SZwvUFfM
It should work if you paste this from notepad into the authorized keys file on your server. For a more detailed explanation, go to the following page:

There are no supported authentication mechanisms for SSH public keys (server sent public key)