NO LANGUAGE DEFINED + Can't Login
Re: NO LANGUAGE DEFINED + Can't Login
Please check session folder:m4th3us wrote:PHP message: PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of $sta-php.sock:", host: "xx.xx.xx.xx:8083", referrer: "https://xx.xx.xx.xx:8083/login/"
/usr/local/vesta/php/etc/php-fpm.conf
Code: Select all
php_admin_value[session.save_path] = /usr/local/vesta/data/sessions
Code: Select all
drwxrwx--- 2 admin admin 4096 Jun 28 13:36 sessions
Re: NO LANGUAGE DEFINED + Can't Login
ls: cannot access /usr/local/vesta/data/sessions: No such file or directoryskurudo wrote:Please check session folder:m4th3us wrote:PHP message: PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of $sta-php.sock:", host: "xx.xx.xx.xx:8083", referrer: "https://xx.xx.xx.xx:8083/login/"
/usr/local/vesta/php/etc/php-fpm.conf
Code: Select all
php_admin_value[session.save_path] = /usr/local/vesta/data/sessions
Code: Select all
drwxrwx--- 2 admin admin 4096 Jun 28 13:36 sessions
Should i create a folder?
edit:
mkdir /usr/local/vesta/data/sessions
chown admin:admin /usr/local/vesta/data/sessions
Solved
many thanks
Re: NO LANGUAGE DEFINED + Can't Login
Nice!m4th3us wrote: mkdir /usr/local/vesta/data/sessions
chown admin:admin /usr/local/vesta/data/sessions
Solved
many thanks
Can you tell us about OS and version?
Re: NO LANGUAGE DEFINED + Can't Login
Ubuntu 14.04.4 LTSskurudo wrote:Nice!m4th3us wrote: mkdir /usr/local/vesta/data/sessions
chown admin:admin /usr/local/vesta/data/sessions
Solved
many thanks
Can you tell us about OS and version?
3.13.0-76-generic x86_64
The problem happen after update using APT
Re: NO LANGUAGE DEFINED + Can't Login
session data files are stored in /tmp
check the permissions.
check the permissions.
Re: NO LANGUAGE DEFINED + Can't Login
In .16 - nope, VestaCP have separate folder for sessions.parsap88 wrote:session data files are stored in /tmp
check the permissions.
Re: NO LANGUAGE DEFINED + Can't Login
Thanks!XoXiLhJ0mn wrote: I have had this problem in a fresh installation. I checked the scripts and opened a BUG report with BUG Fix here:
https://bugs.vestacp.com/issues/265
It's fixed afaik.