The paths for Additional FTP account(s) don’t seem to work properly.
I noticed the issue described here, but the topic was supposedly solved and closed: Additional FTP account root path problem . The user solved it by copy-pasting the old config, blaming it on vsftpd’s new configuration, but I found it’s HestiaCP’s very own config that includes said issue (hestiacp/install/deb/vsftpd/vsftpd.conf at main · hestiacp/hestiacp · GitHub).
Prior, HestiaCP would have chroot_local_user=YES, whereas now it has this:
allow_writeable_chroot=NO
local_root=/srv/jail/%u
user_sub_token=%u
This doesn’t seem to correctly direct the Additional FTP account(s) to the path entered and showing. When I copy (or change it to) the old config, it does work as expected, but I’m not sure if that breaks anything else, and surely it’s not supposed to be that way if Hestia now ships with something differently.
Most notably, and the only reason I ran into this issue, is that this change breaks new installations recovering older backups. Older installations that always kept the old config (as recommended during upgrades) still function as expected, but suddenly all such users ended up in directories they were unfamiliar with.