Every FTP account created in Vesta CP gets associated to /sbin/nologin and therefore won't work.

This is the first server I have built using keys but don’t think that’s where the error lies.

I can get FTP connection using the same Vesta CP admin login details. But other FTP accounts made within domains get linked to /sbin/nologin and return

Status: Connecting to XXX.XXX.XXX.XXX… Response: fzSftp started, protocol_version=7 Command: open “loginuser@ipaddress” 22 Command: Pass: ******* Error: Authentication failed. Error: Critical error: Could not connect to server Status: Disconnected from server


User userlogin not allowed because shell /sbin/nologin does not exist

Dec 3 12:25:51 serverid sshd[26030]: input_userauth_request: invalid user userlogin [preauth]

Dec 3 12:25:51 serverid sshd[26030]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= user=userlogin

Dec 3 12:25:53 serverid sshd[26030]: Failed password for invalid user userlogin from port 56548 ssh2

Dec 3 12:25:53 serverid sshd[26030]: error: Received disconnect from 13: Unable to authenticate [preauth]

First trial was on a fresh install with minor personal configurations (including current updates) Second was a fresh install with only Vesta CP installed

All installs have been on Ubuntu 14.04.5 x64

Yet my current server using the same OS with minor personal configurations and some major updates which have not gone according to plan and causing some funny issues. I can create new FTP users in Vesta CP that associate with /usr/bin/rssh all work.

Thanks in advance.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

I believe that VestaCP uses a standard FTP service rather than SFTP which runs over ssh. The FTP users are created with /sbin/nologin in order to disable shell access via SSH. Instead of connecting to port 22 you should instead try connecting to port 21 with your FTP client.