Remove both files
rm /home/anasilva/.ssh/*
I did, I check the nginx log and still the same information.
Its late in portugal, I’m going to turn off, and retry again everything tomorrow and i will give you feedback !
Thank you a lot for everything, there is a point system here that I can give 10000000 for your mega help ?
1 Like
Good Morning 
I’ve copilled everything you share, and what I did :
rm all /home/$user/.ssh/*
chmod 755 /home/$user/.ssh
chmod 755 /home/$user
setfacl -m “u:$user:r-x” “/home/$user”
setfacl -m “g:hestia-users:—” “/home/$user”
For the Admin user its still working, for the other users it still giving the bellow error.
Note: When I’m logging in the other users, I’m going directly from the Admin page and select the “User menu” and then I select the “User”, on that User I try to use the FM
#4 /usr/local/hestia/web/fm/vendor/league/flysystem/src/Filesystem.php(272): League\Flysystem\Adapter\AbstractFtpAdapter->listContents()
#5 /usr/local/hestia/web/fm/backend/Services/Storage/Filesystem.php(199): League\Fly" while reading response header from upstream, client: 89.115.89.243, server: _, request: "POST /fm/?r=/getdir HTTP/2.0", upstream: "fastcgi://unix:/run/hestia-php.sock:", host: "hestiacp.cenasuteis.com:8083", referrer: "https://hestiacp.cenasuteis.com:8083/fm/"
2023/10/30 08:43:53 [error] 2340#0: *30 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught League\Flysystem\Sftp\ConnectionErrorException: Could not login with username: anasilva, host: 127.0.0.1 in /usr/local/hestia/web/fm/vendor/league/flysystem-sftp/src/SftpAdapter.php:244
Stack trace:
#0 /usr/local/hestia/web/fm/vendor/league/flysystem-sftp/src/SftpAdapter.php(207): League\Flysystem\Sftp\SftpAdapter->login()
#1 /usr/local/hestia/web/fm/vendor/league/flysystem/src/Adapter/AbstractFtpAdapter.php(650): League\Flysystem\Sftp\SftpAdapter->connect()
#2 /usr/local/hestia/web/fm/vendor/league/flysystem-sftp/src/SftpAdapter.php(360): League\Flysystem\Adapter\AbstractFtpAdapter->getConnection()
#3 /usr/local/hestia/web/fm/vendor/league/flysystem/src/Adapter/AbstractFtpAdapter.php(338): League\Flysystem\Sftp\SftpAdapter->listDirectoryContents()
#4 /usr/local/hestia/web/fm/vendor/league/flysystem/src/Filesystem.php(272): League\Flysystem\Adapter\AbstractFtpAdapter->listContents()
#5 /usr/local/hestia/web/fm/backend/Services/Storage/Filesystem.php(199): League\Fly" while reading response header from upstream, client: 89.115.89.243, server: _, request: "POST /fm/?r=/getdir HTTP/2.0", upstream: "fastcgi://unix:/run/hestia-php.sock:", host: "hestiacp.cenasuteis.com:8083", referrer: "https://hestiacp.cenasuteis.com:8083/fm/"
root@hestiacp:~# ls -ld /home/anasilva/.ssh
drwxr-xr-x 2 anasilva anasilva 4096 Oct 30 08:40 /home/anasilva/.ssh
root@hestiacp:~# ls -l /home/anasilva/.ssh
total 8
-rw-r--r-- 1 anasilva anasilva 326 Oct 30 08:40 authorized_keys
-rw------- 1 admin admin 1064 Oct 30 08:40 hst-filemanager-key
root@hestiacp:~# getfacl /home/anasilva
getfacl: Removing leading '/' from absolute path names
# file: home/anasilva
# owner: root
# group: root
user::rwx
user:anasilva:r-x
group::r-x
group:hestia-users:---
group:anasilva:r-x
mask::r-x
other::r-x
Creating a new user works?
Try this:
v-rebuild-user anasilva
If that doesn’t work, try to change shell from nologin to bash
v-change-user-shell anasilva bash
If that works, try to change the shell again to nologin
v-change-user-shell anasilva nologin
I tried the v-rebuild-user anasilva and it worked !.
After that I place again the backup from the day 29, and tried again to use the v-rebuild-user anasilva and its working.
Tried with the other users and success.
So the rebuild did fix !! 
thank you a lot !!!
Do you have 2min to explain what happend ?
I Know that this is not a problem on HestiaCP, it was a problem that I introduce after I restore a full system.
1 Like
I don’t know what was causing it but rebuild does a lot of things, changes perms, adds user, group, dirs, etc.
This works for me aswell, new users it works fine but backup restored uses it does not for some reason. (had this issue for along time).
Its wierd that you have to run the command twice or more to get it working.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.