SOLVED WordPress Toolkit error Could not create new 'wp-config.php' file.

[tpartzard]

I can't install wordpress via wordpress toolkit

Here are some errors I found in the wordpress toolkit logs.

[2022-08-01 06:08:26.504] DEBUG Rollback WordPress installation of instance #1913: remove from WPT database
[2022-08-01 06:08:26.518] DEBUG Execute shell command: 'rm -rf /usr/local/cpanel/3rdparty/wp-toolkit/var/logs/action-logs/0989f26c-276f-4e54-b60f-0ba3f67d6de7'
[2022-08-01 06:08:26.527] DEBUG Exit code: '0'
Command output: ''
[2022-08-01 06:08:26.536] ERROR Error: Could not create new 'wp-config.php' file.[2022-08-01 06:08:26.536] DEBUG PleskExt\WpToolkit\Exception\WpCliExecutionException: Error: Could not create new 'wp-config.php' file.
in /usr/local/cpanel/3rdparty/wp-toolkit/plib/library/Capability/WpCli/WpCliUtils.php:42
Stack trace:
#0 /usr/local/cpanel/3rdparty/wp-toolkit/plib/library/Capability/WpCli/LocalCpanel.php(145): PleskExt\WpToolkit\Capability\WpCli\WpCliUtils::throwWpCliExecError('Error: Could no...', 'Unix', '')
#1 /usr/local/cpanel/3rdparty/wp-toolkit/plib/library/Capability/WpCli/WpCli.php(140): PleskExt\WpToolkit\Capability\WpCli\LocalCpanel->call(Array, '{"WORDPRESS_PRO...', Array, false, NULL)

 

[cPRex]

Hey there! Is it possible there is already a WordPress site or a wp-config.php file on the account? Although no sites are linked to WordPress Toolkit yet according to your screenshot, a manual installation that hasn't been linked is still possible, and that would cause this error.

As a test, you could try installing WordPress in a different directory to see if that works well. If that does work, the problem is with something specific to the original installation directory.

 

[tpartzard]

Hey there! Is it possible there is already a WordPress site or a wp-config.php file on the account? Although no sites are linked to WordPress Toolkit yet according to your screenshot, a manual installation that hasn't been linked is still possible, and that would cause this error.

As a test, you could try installing WordPress in a different directory to see if that works well. If that does work, the problem is with something specific to the original installation directory.

I have installed it in a new directory and tested it on a new account, but still the same issue.

 

[cPRex]

That's definitely odd - if you have root access could you open a support ticket with our team so we can take a look at this?

 

[tpartzard]

That's definitely odd - if you have root access could you open a support ticket with our team so we can take a look at this?

Sorry, my company has a security policy for access. But if you want to see the configuration or log about it I can provide.

 

[cPRex]

I did reach out to the WordPress Toolkit team, and they were also not familiar with this error. Our support team would be able to provide you with a list of IP addresses for server access, so you wouldn't have to open up SSH or WHM globally, if that would ease some concerns about submitting a ticket, but it seems we may be in uncharted territory here.

 

[tpartzard]

I did reach out to the WordPress Toolkit team, and they were also not familiar with this error. Our support team would be able to provide you with a list of IP addresses for server access, so you wouldn't have to open up SSH or WHM globally, if that would ease some concerns about submitting a ticket, but it seems we may be in uncharted territory here.

I've already opened a ticket to your support team. The issue caused by imunify360 generated a rule preventing /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/config-command/src/Config_Command.php

Thank you very much for support.

 

[cPRex]

I'm glad we were able to help track that down!

 

[HostXNow_Chris]

I started noticing this issue.

cPanel promotes Imunify360. Why on earth would Imunify360 start blocking a process from cPanel WordPress Toolkit!? It can make the web host look at fault.

So the solution is to

Ignore detected rules for those files

Path: /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/config-command/src/Config_Command.php
Rules: Auto Immunity rule generated on 2023-02-28 18:14:16.303399

Here's an idea, as cPanel/Imunify360 are partners, why don't cPanel ask Imunuify360 to whitelist the above automatically?

 

[HostXNow_Chris]

Seems Config_Command.php is not the only process that is blocked. Checking further with Imunify360.

 

[cPRex]

I don't hate the idea of being a bit more collaborative and seeing if we can fix some things before they are an issue, but let me know what Imunify has to say and we can go from there!

 

[HostXNow_Chris]

CloudLinux/Imunify360 have now corrected this on their product.

Thank you for the provided information. We have added cpanel scripts to PHP Immunity whitelist. The rules on your server will be updated automatically.

 

[cPRex]

Nice!