Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've a Ubuntu machine where is installed OpenSSH.

I want upload/download files there thru SFTP with FileZilla.

SSH works good with putty etc, but when I try to connect with FileZilla, I get

Status: Connecting to A.B.C.D...
Response:   fzSftp started
Command:    open "user@A.B.C.D" 22
Command:    Pass: ****
Status: Connected to A.B.C.D...
Error:  Out of memory!
Error:  Could not connect to server

Here's about it

but I didn't understood how to fix it or what to do?

share|improve this question
up vote 4 down vote accepted

This is probably caused by one of your login scripts on the Ubuntu machine that is generating output to places it should never output to. (It's like using the sink instead of the bathroom... I bet your room mate will run out of memory tolerance pretty soon.) PuTTY has a FAQ section about it. Read it here.


A.7.6 When attempting a file transfer, either PSCP or PSFTP says ‘Out of memory’ and dies.

This is almost always caused by your login scripts on the server generating output. PSCP or PSFTP will receive that output when they were expecting to see the start of a file transfer protocol, and they will attempt to interpret the output as file-transfer protocol. This will usually lead to an ‘out of memory’ error for much the same reasons as given in question A.7.5.

This is a setup problem in your account on your server, not a PSCP/PSFTP bug. Your login scripts should never generate output during non-interactive sessions; secure file transfer is not the only form of remote access that will break if they do.

On Unix, a simple fix is to ensure that all the parts of your login script that might generate output are in .profile (if you use a Bourne shell derivative) or .login (if you use a C shell). Putting them in more general files such as .bashrc or .cshrc is liable to lead to problems.

share|improve this answer
One other solution is to pipe the output of any commands in your .bashrc to /dev/null. – palehorse Oct 25 '12 at 14:22

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.