Getting a few Fatal Errors

Hi! This is unexpected. It seems shell_exec is available, but returns null. Then the uapi command may not be in path enironment on the server, so must use the full path. If you can edit files:

Change line 14 of includes/UAPI.php
private const uapi = 'uapi';//'/usr/local/cpanel/bin/uapi';
to
private const uapi = '/usr/local/cpanel/bin/uapi';
If that helps, great, it explains it fully, so please get back here and I’ll try detect what’s correct for each Linux distribution and cPanel configs, ready for next version.

Or just, or if above does not help, try add this to your wp-config.php to force try communicating over HTTP instead:
const WF_CPANEL_SHELL_EXEC_DISABLE = true;
and this should bring up a message (not fatal error) about whats missing. See Details page here:

If the shell_exec function is disabled in your PHP config, add this line to your wp-config.php file:
const WF_CPANEL_API_TOKEN = 'paste-your-api-token';
See [Manage API Tokens in cPanel?](https://docs.cpanel.net/cpanel/security/manage-api-tokens-in-cpanel/ )

Then og into your cPanel manuaaly, once, create an API Access Token as described, and paste it into the config line shown above, save. It should then just work. The config line can be removed later, after creating a new access token from wp-admin, “cPanel Token Management” – an automated process.

In 4.4.16 a null return causes the plugin to assume not on cPanel, to avoid this.

Also, the line to test should now be:
public const uapi = '/usr/local/cpanel/bin/uapi';

A check for this is now included in v4.5.
If that won’t work, I hope you can check that you are really hosted on cPAnel. If not, this plgin can do nothing but give a proper error message.