VestaCP “NO LANGUAGE DEFINED” Login Fix

“Language Not Defined” can be a very frustrating problem that can occur with VestaCP when trying to login, it doesn’t any information on what the problem is or how to get around it. The good news is that it is a relatively easy fix most of the time and the cause can be easily avoided.



Why does it occur?

To put it simply the error occurs because the servers storage is completely full or the innode limit has been reached. This can be caused by storing too many backups on your VestaCP accounts or a user using too much storage space. The innodes may be used up by many small files.

The other, less common reason, is that the admin users “quota” has been filled accidentally. This is a bit more involved to fix but we’ll be going over that next afterwards.


So how do I fix it? I need to access my admin panel!

Login to your servers root user account or another account with sudo privileges. Once you’re logged in we’ll start diagnosing the problem.

We’ll start by checking the servers disk space since it’s the most common cause of the “language not defined” error. To do this, run the following command in the terminal.

df -h

This will check the servers disk space.

[[email protected] ~]# df -h
 Filesystem Size Used Avail Use% Mounted on
 /dev/vda1 25G 15G 8.6G 64% /
 devtmpfs 1.4G 0 1.4G 0% /dev
 tmpfs 1.4G 0 1.4G 0% /dev/shm
 tmpfs 1.4G 161M 1.3G 12% /run
 tmpfs 1.4G 0 1.4G 0% /sys/fs/cgroup
 tmpfs 285M 0 285M 0% /run/user/0

As you can see on my output, I have 0G space free which is why I’m getting the error. So to fix this I’m going to try removing some backups since these take up the most space on my system. If you have space available then skip the rest of this section and move onto the quota fix.

VestaCP stores user backup files in the “/home/backup” folder. Change into the backup folder with the command

cd /home/backup

Now I’m going to see what’s in the folder with the “ls” command with a parametre to show the file size in a readable format.

ls -lh

And I get the following output.

[[email protected] backup]# ls -lh
 total 8.7G
 -rw-r----- 1 admin rocket 196M Aug 10 05:10 rocket.2017-08-10.tar
 -rw-r----- 1 admin rocket 157M Aug 11 05:10 rocket.2017-08-11.tar
 -rw-r----- 1 admin rocket 161M Aug 12 05:10 rocket.2017-08-12.tar
 -rw-r----- 1 admin rocket 162M Aug 13 05:10 rocket.2017-08-13.tar
 -rw-r----- 1 admin rocket 166M Aug 14 05:10 rocket.2017-08-14.tar
 -rw-r----- 1 admin rocket 167M Aug 15 05:10 rocket.2017-08-15.tar
 -rw-r----- 1 admin rocket 167M Aug 16 05:10 rocket.2017-08-16.tar
 -rw-r----- 1 admin rocket 167M Aug 17 05:10 rocket.2017-08-17.tar
 -rw-r----- 1 admin rocket 167M Aug 18 05:10 rocket.2017-08-18.tar
 -rw-r----- 1 admin rocket 168M Aug 19 05:10 rocket.2017-08-19.tar
 -rw-r----- 1 admin rocket 167M Aug 20 05:10 rocket.2017-08-20.tar
 -rw-r----- 1 admin rocket 170M Aug 21 05:10 rocket.2017-08-21.tar
 -rw-r----- 1 admin rocket 173M Aug 22 05:10 rocket.2017-08-22.tar
 -rw-r----- 1 admin rocket 173M Aug 23 05:10 rocket.2017-08-23.tar
 -rw-r----- 1 admin rocket 174M Aug 24 05:10 rocket.2017-08-24.tar
 -rw-r----- 1 admin rocket 173M Aug 25 05:10 rocket.2017-08-25.tar
 -rw-r----- 1 admin rocket 174M Aug 26 05:10 rocket.2017-08-26.tar
 -rw-r----- 1 admin rocket 173M Aug 27 05:10 rocket.2017-08-27.tar
 -rw-r----- 1 admin rocket 174M Aug 28 05:10 rocket.2017-08-28.tar
 -rw-r----- 1 admin rocket 173M Aug 29 05:10 rocket.2017-08-29.tar
 -rw-r----- 1 admin rocket 173M Aug 30 05:10 rocket.2017-08-30.tar
 -rw-r----- 1 admin rocket 174M Aug 31 05:10 rocket.2017-08-31.tar
 -rw-r----- 1 admin rocket 173M Sep 1 05:10 rocket.2017-09-01.tar
 -rw-r----- 1 admin rocket 174M Sep 2 05:10 rocket.2017-09-02.tar
 -rw-r----- 1 admin rocket 174M Sep 3 05:10 rocket.2017-09-03.tar
 -rw-r----- 1 admin rocket 174M Sep 4 05:10 rocket.2017-09-04.tar
 -rw-r----- 1 admin rocket 174M Sep 5 05:10 rocket.2017-09-05.tar
 -rw-r----- 1 admin rocket 174M Sep 6 05:10 rocket.2017-09-06.tar
 -rw-r----- 1 admin rocket 174M Sep 7 05:10 rocket.2017-09-07.tar
 -rw-r----- 1 admin rocket 174M Sep 8 05:10 rocket.2017-09-08.tar
 -rw-r----- 1 admin rocket 174M Sep 9 05:10 rocket.2017-09-09.tar
 -rw-r----- 1 admin rocket 174M Sep 10 05:10 rocket.2017-09-10.tar
 -rw-r----- 1 admin rocket 174M Sep 11 05:10 rocket.2017-09-11.tar
 -rw-r----- 1 admin rocket 174M Sep 12 05:10 rocket.2017-09-12.tar
 -rw-r----- 1 admin rocket 174M Sep 13 05:10 rocket.2017-09-13.tar
 -rw-r----- 1 admin rocket 174M Sep 14 05:10 rocket.2017-09-14.tar
 -rw-r----- 1 admin rocket 175M Sep 15 05:10 rocket.2017-09-15.tar

Now I can see that a lot of backups from August are taking space up on my system that could be freed up. I’m going to delete the backups taken in August to reclaim some space since they’re quite old and I have offsite copies available. Since the owner of the backups is “rocket” and the date of the files is in the name I can use the “rm” command and the “*” which is used to apply to anything.

To do this I’m going to run the command

rm rocket.2017-08*

This will delete anything taken in August clearing up space so that I can login. Be careful using the rm command as you can damage your system if used incorrectly.

After doing this I’m now able to login to my VestaCP installation again like normal!


I already have disk space free and I still can’t login!

No problem! We need to just reset the aministrator account’s disk quota.

To do this run the following command, it will open a configuration file in nano that we’re going to edit.

nano /usr/local/vesta/data/users/admin/user.conf

Now go down to the “DISK_QUOTA='” section and change it to

DISK_QUOTA='unlimited'

Now that’s done save and exit the file, then refresh the account with this command

v-update-user-quota admin

Try logging in again, if you still receive the error then try restarting MySQL or your server, you should be able to login again, just like before!


Still having an issue logging in? Leave a comment and I’ll try to help you 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *