This was working well until a couple of days ago. I can't recall having done anything to the server leading it to start closing the connection. Also I have no idea what exitcode 128 means, and can't find anything about it. Here's FileZilla's response to the connection attempt

Status: Connecting to foo.bar.no...
Response:   fzSftp started
Command:    open "root@foo.bar.no" 22
Command:    Pass: *******
Status: Connected to foo.bar.no
Error:  Connection closed by server with exitcode 128
Error:  Could not connect to server

Trying to connect with WinSCP also tells me the server closed the connection with error code 128 and additionally tells me:

Cannot initialize SFTP protocol. Is the host running a SFTP server?

I can SSH connect to the server with problem using PuTTY. Any ideas?

link|improve this question

78% accept rate
feedback

2 Answers

Since it was working before, have you tried restarting the service? Another thing that you may want to try is using passive mode for your connection. Also, try either resetting the password or creating a new user account (your current account may be locked).

link|improve this answer
I've tried rebooting the server and using passive mode. I've also tried changing the password which I don't see why would have worked, since I can log into SSH using PuTTY. Also this is the root account, so how can it be locked? :P – Codemonkey Jan 20 at 2:29
feedback

Looks like a permissions issue to me. Can your user account access whatever ftp folder your configured to access at login time? Do both you and root (or whatever account is running the ftp/ssh services) have access to your home directory and/or custom ftp directory?

link|improve this answer
My user account is root :P In addition, this netstat line shows that root is also running ssh tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN root 3960 1130/sshd. – Codemonkey Jan 20 at 2:31
feedback

Your Answer

 
or
required, but never shown

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