How to Fix WP Toolkit Initial Data Load Error (WHM)

Updated By - July 9, 2025

Are you seeing this error in WHM’s WordPress Toolkit on AlmaLinux?

Initial data load error: some required fields are not provided

You're not alone — this is a fairly common issue in WP Toolkit. Follow this step-by-step guide to fix it and get your WP Toolkit interface working again.

fix wp toolkit initial data load error whm cpanel

Quick Fix (TL;DR)

If you're in a hurry, try these common fixes:

  • Correct ownership and permissions: 
    chown -R root:root /usr/local/cpanel/3rdparty/wp-toolkit/var
chmod -R 755 /usr/local/cpanel/3rdparty/wp-toolkit/var
  • Reinstall WP Toolkit: 
    yum reinstall wp-toolkit-cpanel -y
  • Restart the WP Toolkit background services: 
    /usr/local/cpanel/3rdparty/bin/supervisorctl restart wp-toolkit

Understanding the WP Toolkit Error

If you're encountering this message in WHM’s WP Toolkit:

Initial data load error: some required fields are not provided

…it typically indicates a permissions issue or missing background services. Let’s walk through a more thorough troubleshooting process.

Symptoms

  • WP Toolkit shows an error immediately upon loading in WHM.
  • No logs under /usr/local/cpanel/3rdparty/wp-toolkit/var/logs/.
  • Running supervisorctl returns “No such file or directory.”
  • Background services for WP Toolkit are not running.

Possible Causes

  • Incorrect ownership of the WP Toolkit's internal runtime directory (e.g., owned by salt instead of root).
  • Missing or broken supervisorctl utility.
  • Partially installed or corrupted WP Toolkit package.

Step 1: Check Installation and Permissions

1. Verify WP Toolkit is installed:

rpm -qa | grep wp-toolkit

2. Check ownership of the var directory:

ls -ld /usr/local/cpanel/3rdparty/wp-toolkit/var

If it’s owned by anything other than root:root (e.g., salt:salt), fix it:

chown -R root:root /usr/local/cpanel/3rdparty/wp-toolkit/var
chmod -R 755 /usr/local/cpanel/3rdparty/wp-toolkit/var

Step 2: Check for supervisorctl

Check if the background service manager exists:

ls -l /usr/local/cpanel/3rdparty/bin/supervisorctl

If it doesn't exist, the WP Toolkit or its dependencies are likely broken.

Step 3: Reinstall or Update WP Toolkit

Try updating WP Toolkit:

yum update wp-toolkit-cpanel -y

If it’s already up-to-date and the issue persists, do a reinstall:

yum reinstall wp-toolkit-cpanel -y

This typically restores any missing files, including supervisorctl.

Step 4: Restart WP Toolkit Background Services

Once supervisorctl is available, restart WP Toolkit’s background services:

/usr/local/cpanel/3rdparty/bin/supervisorctl restart wp-toolkit

Check the status:

/usr/local/cpanel/3rdparty/bin/supervisorctl status

Step 5: Confirm WP Toolkit is Working

  • Reload the WP Toolkit interface in WHM.
  • If it still fails, run a manual scan:
/usr/local/cpanel/3rdparty/wp-toolkit/scripts/scan-all

Additional Notes

  • Make sure the salt user does not own WP Toolkit directories (this was an issue that got me after moving servers).
  • Permissions issues often stem from failed updates or conflicts with tools like SaltStack.
  • Keeping WP Toolkit and its dependencies updated helps prevent such errors.

Summary On Fixing The WP Toolkit Error

To fix the "initial data load" WP Toolkit error that appears in WHM/Cpanel:

  • Correct directory permissions and ownership.
  • Restore the missing supervisorctl tool.
  • Reinstall or update the WP Toolkit package.
  • Restart background services and verify functionality in WHM.

Frequently Asked Questions (FAQ)

What causes the "Initial data load error" in WP Toolkit?

This WP Toolkit error typically appears due to incorrect permissions, missing services (like supervisorctl), or a partially installed WP Toolkit package on WHM/cPanel.

How do I check if supervisorctl is missing?

Run ls -l /usr/local/cpanel/3rdparty/bin/supervisorctl. If the file doesn't exist, it's likely that the WP Toolkit or its dependencies are broken and need to be reinstalled.

Can I fix this without reinstalling WP Toolkit?

Yes, sometimes just correcting directory permissions and restarting the WP Toolkit service is enough. However, if core files are missing, a reinstall is necessary.

Is it safe to change ownership to root:root for WP Toolkit folders?

Yes. WP Toolkit directories should be owned by root:root. If they are owned by salt or another user, you should correct it using chown.

Will updating WP Toolkit cause downtime for WordPress sites?

No, updating or reinstalling WP Toolkit plugin affects the WHM interface tools but does not take WordPress sites offline.

Helpful Resources

If you want to dive deeper into the tools and systems mentioned in this guide, here are some trusted external resources:

Similar Network Hosting Solutions