It seems that there is something wrong with the inode counter, it says you have 0 inodes which you can see in the file manager is clearly not true.
I tried to add a script that can count the number of inodes in your website, but I couldn’t because it doesn’t appear to be possible to upload files over FTP anymore. When I tried it with FileZilla, I saw the following error:
553 Can’t open that file: Disk quota exceeded
The “Disk quota exceeded” error means you either have more than 5 GB of files, or more than 30,000 inodes.
So you’ll need to remove some stuff from your account to fix your account.
Oh, ant the error changed. No more Error 500. Now it’s more clear:
It appears your account has fully used it’s inode allocation, you will need to delete files to reduce inodes before the script installer will work, or upgrade to premium hosting where we offer over 400,000 inodes !
Because the inode counter counts files and directories. If you use a CMS, it often has many thousands of files just for the software itself. And this can go up rapidly once you start installing plugins.
So your website may have 10k+ files and directories before you’ve ever created your first post or page.
And posts and pages tend to be stored in in the database and may not affect your inode usage at all.
For most sites, inodes don’t count “content”, they count software.
I’ve deleted all files from this account, all databases too. Only 1 empty directory is present, 0 KB of files. 2 inodes used.
Second account, Wordpress and plugins, 123,7 MiB and 7926 files. Control panel statistics: Disk Space Used: 0 MB, Inodes Used: 0 % (0 of 30019).