After entering the info, it gives this error: “An error occurred while updating Disable Admin Notices Individually: Could not create directory. /htdocs/wp-content/upgrade/disable-admin-notices”. The same error appears on multiple plugins.
This issue also seems to affect image and file uploads as well, giving an error stating “The uploaded file could not be moved to wp-content/uploads/2024/08.”
Other Information
After browsing the forums a little bit, it seems that this behavior is similar to when the site has no inodes remaining; however, I checked, and I’ve only used 30% so far. Any help would be great!
Also, I would add more images, but the forum won’t let me.
Using FTP to manage files should not be necessary. WordPress can write to its own files, and doing local file operations is faster and more reliable than going through FTP.
I get that you tried to to try and fix the file management issue. But now you know that switching to FTP doesn’t solve it, I suggest to revert the change.
As for the issue itself, if I try to create a directory on your account with FTP, I see the error:
550 Can’t create directory: Disk quota exceeded
Which does suggest that you have hit a limit.
Inode usage is fine. However, the disk usage is looking very weird.
If the Disk Quota and Disk Space Used are correct, then you have reached the 5 GB disk space limit. The Disk Free limit then makes no sense.
Looking further in your account, I see you have a few very large backup files stored in the htdocs/wp-content/backups-dup-pro folder. So:
Please remove the stored backups. We don’t allow our hosting to be used for backup storage, and doing so will reduce your disk space to normal limits.
The name of the folder suggests you’re using Duplicator Pro, which starts at $99 per year. If you’re willing to spend that much on a backup plugin, you really should not be using free hosting. And if you didn’t pay for the plugin, stop using it immediately, because pirated plugins are very illegal and very dangerous, and good free options exists.
Please note that creating backups is quite stressful on the server storage, and will generate high IO usage on your account. This risks getting your account suspended.
There’s no need to revert anything, given the fact that there’s no options to start with.
WP_Filesystem will always fallback to FTP / SFTP when it determined that it cannot access the filesystem directly. And yes, it doesn’t store FTP / SFTP credentials, assuming that you would fix the permission issue later.
