Plesk for Linux kb: technical ABT: Group B
- Plesk for Linux
Unable to connect to Plesk server via SFTP with the error (e.g. from FileZilla):
CONFIG_TEXT: Error: Authentication failed.
Error: Critical error: Could not connect to server
The following error is observed in
CONFIG_TEXT: proftpd: pam_env(proftpd:setcred): Unable to open
config file: /etc/security/pam_env.conf: Permission denied
proftpd: pam_systemd(proftpd:session): Failed to connect to system bus: Permission denied
proftpd: pam_unix(proftpd:session): session closed for user user
Received unexpected end-of-file from SFTP server
The system user of the subscription is used to log in over SFTP
Access to the server over SSH is set to Forbidden in Domains > example.com > Web Hosting Access.
- Log into Plesk
- Navigate to Plesk> Domains > example.com > Web Hosting Access
- Make sure that the field Access to the server over SSH is set to any available shell (but not to Forbidden).
This option is not available at my license level, but remote users fail authentication. ftp from localhost works fine. It makes no sense in any way shape or form since other users can login just fine
Let me elaborate on my situation.
I'm trying to setup individual user key files.
I setup the root user with zero issue.
Plesk does not create a /home/user directory, so I can't put the key files for users in their own folder.
Using command line only on my other Ubuntu server without Plesk installed I am able to correctly configure the server to use individual key files @ /home/user/.ssh in about 1 minute for each user.
Using Plesk I am unable to do so after 2 hours of research.
This is not why I'm getting the error. I have already setup the user account exactly as shown here and still continue to get the "Could not connect to server" error. Yes, passwords have been checked a million times and I can login directly to Plesk with the password that fails on SFTP.
This "help" article is akin to, "You figure it out yourself".
So, please elaborate on other causes.
We're all waiting, paying money for something that isn't working at all. We don't like to pay for non-working tech. Should we all switch to cPanel?
Please sign in to leave a comment.