Moved DA Accounts to New Server, Can No Longer SFTP into Accounts

[open4biz]

This may be an easy question, but what are common reasons for the following SFTP login error messages:

Error: Authentication failed.
Error: Critical error
Error: Could not connect to server

I changed all the passwords and verified they're the expect values. I checked the firewall and the port they're connecting on is open.

I've verified the users I'm trying to SSH in with are allowed in the ssh config file. I noticed PAM authentication isn't turned off yet, per ConfigServer Firewall's recommendations, but I'll get to that today.

Other than that, is there something obvious I'm overlooking? This problem hasn't cropped up the past two server moves so I'm thinking it's something simple?

Thanks,

Ansel

 

[zEitEr]

Hello,

Is that OpenSSH or ProFTPd that serves SFTP for you?

 

[open4biz]

I think OpenSSH? I noticed a configuration setting in sshd.conf which mentioned tunneling. I enabled it and now it works. Do you think I need to configure anything in ProFTPd?

 

[zEitEr]

On what port do you try to login? And what service is bind to that port on both servers?

To buil ProFTPd with SFTP support please follow this guide: http://help.directadmin.com/item.php?id=439

 

[open4biz]

Port 25250, it is configured in SSH's config file and stayed the same across the old and new servers.

 

[open4biz]

Thank you for your help, by the way.

 

[zEitEr]

OK, I see. Then you need to check and compare /etc/ssh/sshd_config on both servers, are they the same? And try to run SSH in a debug mode:

Enter the following command from the bash prompt:

/usr/sbin/sshd -p <listening port> -D -d -e

This will start openssh daemon in standalone debug mode and messages will be displayed on the screen. You may specify up to three -d for increased output verbosity.

Be carefull not to lock yourself out of your server. You may run SSHd in a debug mode as the second intance on another port, there is no need to stop running processes of sshd.