Vesta Control Panel - Forum

I had the same problem (CentOS 6.4). Everything is updated with 'yum update'.

'chmod 777 /var/lib/php/session' helps to solve this problem. But can it cause any security issues?

blackyangell wrote:I had the same problem (CentOS 6.4). Everything is updated with 'yum update'.
'chmod 777 /var/lib/php/session' helps to solve this problem. But can it cause any security issues?

It's all recommended method - if you still worry. try to change permissions to 775 / 770

I still get the blowfish_secret warning inside panel. Any ideas?

chmod 777 /var/lib/php/session/ did the trick to solve the login screen error.

I'm not sure if this information is relevant to you all, but check out Stack Overflow: http://stackoverflow.com/questions/3694 ... phpmyadmin

If that bug sounds like you, then read on:

EDIT: Read my next comment, which is a better fix (& fixes a slew of other problems on a blank vestacp install): viewtopic.php?f=14&t=7500&p=28169#p28169

If, like me you are running Ubuntu 14.04 (& probably others), and having DB issues with "can't login", then the problem seems to be due to the mysql config missing a "bind-address" setting.

Edit /etc/mysql/my.cnf and add the missing "bind-address" line to the [mysqld] section:
After making the change, don't forget to restart mysql:
This fixes 3 issues in one go:
1. can't login to myphpadmin
2. roundcube "DATABASE ERROR"
3. can't create a DB from the vestacp

PS: This bug appears when you install vestacp on a blank ubuntu machine (ie nothing installed, but maybe openssh).

I have exactly the same problem with the session. And after fix the issue I found this post with the same fix. I lose an hour because I don't do a search here in this forum :/

I solved this problem without chmod the sesion folder to 777. Please correct me if I'm wrong here:

I think during installation of VestaCP, some of the configuration files were set to belong to admin owner. So, I changed the session folder to owner 'admin' and it works.

This method works for the blowfish part too. The configuration file, /etc/phpMyAdmin/config.inc.php need to be admin owner from the folder phpMyAdmin.

arafatx wrote:I solved this problem without chmod the sesion folder to 777. Please correct me if I'm wrong here:
I think during installation of VestaCP, some of the configuration files were set to belong to admin owner. So, I changed the session folder to owner 'admin' and it works.

Something like this. With installation/upgrade latest phpmyadmin from repo appear this bug (in centos/rhel only). Debian/Ubuntu not have this bug.

skurudo wrote:

arafatx wrote:I solved this problem without chmod the sesion folder to 777. Please correct me if I'm wrong here:
I think during installation of VestaCP, some of the configuration files were set to belong to admin owner. So, I changed the session folder to owner 'admin' and it works.

Something like this. With installation/upgrade latest phpmyadmin from repo appear this bug (in centos/rhel only). Debian/Ubuntu not have this bug.

When this bug will be fixed? I love VestaCP a lot.

arafatx wrote: When this bug will be fixed? I love VestaCP a lot.

Dunno, may be with new update phpmyadmin.