skullx wrote: ↑

Sat Oct 26, 2019 11:58 pm

I am currently running CentOS7, and vestaCP Ver. 0.9.8 Rel 26.
After using Filezilla to login using my one of my FTP users, I lost access to the VESTACP Panel.
At first I get "505 internal error" page.
I stopped the vesta service, restarted it, and then I could get to the panel, however, when I try to login with the admin or the root user I still get "invalid login".
So I ran a status, and then get:
pam_unix (sudo:auth) : auth could not identify password for [ftp_user_account]
ftp_user_account : user NOT in sudoers ; TTY=unknown ; PWD=/usr/local/vesta/web/login...es json
pam_unix(sudo:auth): conversation failed
Please help as I even rebooted the server with no luck. Did you ever get a solution on this? The same thing happens to me also. It usually takes a couple of hours for me to regain access to the panel.

This has been happening to me too every time i ftp with Filezilla (I have not tried other clients)
OS: CentOS 7
The only method to fix this issue that works for me is to stop vesta service and then start again (make sure you exit/close filezilla ftp session first)

Just a guess, but if access is restored after 'a couple of hours', could it be fail2ban blocking your ip address? Check in the fail2ban log.
If you have a static IP, you can also add it to fail2ban local.conf to whitelist it.