myVesta can't login after install

[infiinite]

Hi dpeca,

I've just installed myVesta on a fresh os and now I'm unable to log in on to my web panel.
This is the second time it has happened

Code: Select all

Congratulations, you have just successfully installed myVesta Control Panel

myurl
username: admin
password: eQvF0xlwAZE8YHCicrXIfFyMyH12BdDr

We hope that you enjoy your installation of myVesta. Please feel free to contact us anytime if you have any questions.
Thank you.

--
Sincerely yours
myvestacp.com team

root@10925150:~# /usr/local/vesta/bin/v-check-user-password admin eQvF0xlwAZE8YHCicrXIfFyMyH12BdDr
/usr/local/vesta/bin/v-check-user-password: line 18: /func/main.sh: No such file or directory
/usr/local/vesta/bin/v-check-user-password: line 19: /conf/vesta.conf: No such file or directory
/usr/local/vesta/bin/v-check-user-password: line 31: check_args: command not found
/usr/local/vesta/bin/v-check-user-password: line 32: is_format_valid: command not found
Error: password missmatch
/usr/local/vesta/bin/v-check-user-password: line 37: /log/auth.log: No such file or directory
root@10925150:~# 

This is what I get when I paste the password in the check user password file right after the install.

[myVesta]

viewtopic.php?f=17&t=49

[infiinite]

Thanks dpeca,

however, I still can't log in to the web panel.

The login page just reloads without any error

Code: Select all

root@media1:~# /usr/local/vesta/bin/v-check-user-password admin eQvF0xlwAZE8YHCicrXIfFyMyH12BdDr
root@media1:~# 

Running the password check didn't give me any output either

[myVesta]

What version of Debian?
What browser you are using?

try to change password with:
passwd admin

If it's not working, send me credentials on private message.

[myVesta]

It could be that some extension in your browser is cutting "HTTP_ORIGIN" header.
Try with other browser.

[infiinite]

Thanks dpeca, you're a saviour.

I'm using Debian 10, and Chrome 92.0.4515.159.

I removed some old extensions and cleared all the data for my panel's domain and now the login is working perfectly fine.

Idk exactly which extension was causing the issue or if it was some other cookies from some other subdomain from the site.