Vesta, myvesta & Hestia all have an annoyance that login ssh access is turned off by default, and newbies always struggle with this, because the solution is hidden, in the advanced section, where you can then turn it on to: bash. That’s what I have always done, but now that I’ve switched to hestia, even this isn’t solving the issue. When I use WinSCP, my fav file manager, it gets failure error:
"server sent command exit status 127.
Googling it for answers, I then changed the winSCP setting for this login, from SFTP, to SCP.
SCP worked! But SFTP is said to be better. It worked fine with myvesta, etc. Can it not work on hestia? Or a hidden setting to turn it on?
Also, I don’t see a setting in hestia to allow me to give various users ftp or sftp access?
It’s a bug:
sed -i 's/internal-sftp-.*/internal-sftp/' /etc/ssh/sshd_config
systemctl restart ssh
And try again.
1 Like
I think it’s a good policy to restrict ssh access by default. Anyway, you can create your own package and in SSH Access option, select bash instead of nologin and all users created with that package will have ssh access by default.
2 Likes