Hi!
In prior versions 1.8.* we could set exact folder, e.g. /public_html, on additional ftp accounts. And created ftp account’s folder structure was as expected - all what included in public_html.
But now it gives us /home/{ftp_user_name}/public_html and additional /tmp folder. I believe it is bug and not some kind of innovation.
Could someone please give clarification about this? And how to avoid this new behaviour?
I’ve had a quick check on my test server and can mostly confirm your observation.
When I leave the path of the ftp user empty, the directory /home/{ftp_user_name} contains all the directories of the the hestia user to whom the ftp users belongs.
When I enter
public_html in the FTP user path, the folder /home/{ftp_user_name} just contains all the files located in the public_html folder of the hestia user.
To be sure You’ve understood me right:
in prevous versions of Hestia there were no unneedable virtual folders like ‘/home/{ftp_user_name}’ and ‘/tmp’ in ftp. We could reach our files quickly just with ‘/’.
This behaviour is from vsftpd’s new configuration. Not from Hestia. Solved by copying vsftpd.conf from old vps.
1 Like