Occasionally, our clients have reported that they cannot access HestiaCP and that their website is not working. This can be due to many problems, but it is generally because the disk is running out of free space due to the websites and backups that are generated automatically.
Check if the problem is disk-related [Basic Level]
The simplest way to detect that the problem is due to a lack of disk space is to access the login panel of HestiaCP, enter the username and the password. If the panel does not load and the option to add a password reappears without showing an error, it means that the server has run out of space.
Check if the problem is disk-related [Advanced Level]
What we need to do is connect via SSH to our server and, once connected, execute the following commands:
# df -h
This command should give us this output:
If we look closely, we will see that /dev/sda2 is at 100% usage, so the disk is full, and this is the reason why it is not possible to log in to HestiaCP or why one of its services is not functioning correctly.
Resolve the issue
The best way to solve the problem is to resize your server's disk. By adding more space to your disk, once the server is restarted, everything will work correctly again. If you have resized the disk and the problem persists, you will likely have to extend the partitions manually.
Another option, if you do not want to resize the disk —since once resized it will remain at that size— is to delete content from the server. There are many places where you can free up space, the first is the directory where HestiaCP stores the backups, located at /backup. There you can delete files and free up space. You can also look to free up space by deleting logs in /var/logs.
We hope this article has helped you. If you have any questions about this or any other issue related to your servers at Clouding, please write to us at support@clouding.io. We are here to help you! 😉