Previously all our web customers were setup to access their SFTP using the shell /bin/bash(chrooted). As of 1-17-17 it was working for everyone. The following monday 1-20-17 it was not. This issue is affecting ALL domains that used /bin/bash(chrooted) as the shell.
When trying to connect, FTP error: EOF while reading packet. Please contact your web hosting service provider for assistance.
When trying to connect via SSH on command line, error: Could not chdir to home directory /var/www/vhosts/domain.com: No such file or directory /usr/local/psa/bin/chrootsh: No such file or directory Connection to domain.com closed.
I can't find any record of any relevant updates to Plesk, I certainly didn't change anything. The only update I see in Plesk history is an update from PHP 7 to PHP 7.0.14. I've been doing some searching, what I found(in below examples, I replaced the actual username with "username" and the actual domain with "domain.com"):
The FTP user in /etc/passwd shows correctly as far as I can tell: username:x:10057:1004::/var/www/vhosts/domain.com:/usr/local/psa/bin/chrootsh
there have been no changes to user or group permissions. The user is correctly assigned to the psacln group, just like before.
The /var/www/vhosts/chroot folder has everything it needs as far as I can tell, and all permissions and ownership are correct.
I have tried the method from Plesk here: https://support.plesk.com/hc/en-us/articles/213909545--HOWTO-How-to-add-new-programs-to-a-chrooted-shell-environment-template, didn't work. I even renamed the chroot folder to chroot_old and reinstalled, no difference.
I have tried adding user-specific rules to the sshd_config file in /etc: Match User username ChrootDirectory /var/www/vhosts/chroot Then restarting sshd, no go.
I also ran the plesk repair utility from this link: https://docs.plesk.com/en-US/onyx/a...epair-utility/plesk-repair-utility-web.74654/ and it found nothing related to my issue.
I have no idea what else to check, and changing the shell to /bin/bash is not an option - besides the security risk we have customers with automated SSH connections that require the chroot for their file/folder pathways. My server support is stumped.
I would appreciate anyone's help!! Thank you.