Skip to main content

New installation using Wordpress Tool Kit fails

jndawson
We are installing a new instance of Wordpress for a customer using the Tool Kit. The public_html was empty when starting. We get these errors (identifying info munged): WordPress was installed with errors: Fatal error: Uncaught Error: Call to undefined function PHPMailer\PHPMailer\mail() in /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php:874 Stack trace: #0 /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php(1923): PHPMailer\PHPMailer\PHPMailer->mailPassthru('USER@ADDRESS.....', 'New WordPress S...', 'Your new WordPr...', 'Date: Tue, 15 F...', NULL) #1 /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php(1657): PHPMailer\PHPMailer\PHPMailer->mailSend('Date: Tue, 15 F...', 'Your new WordPr...') #2 /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php(1493): PHPMailer\PHPMailer\PHPMailer->postSend() #3 /home/USER/public_html/wp-includes/pluggable.php(544): PHPMailer\PHPMailer\PHPMailer->send() #4 /home/USER/public_html/wp-admin/includes/upgrade.php(624): wp_mail(Array, 'New WordPress S...', 'Your new WordPr...', Array) #5 /home/USER/public_html/wp-admin/includes/upgrade.php(117): wp_new_blog_notification('COMPANY', 'https://WEBSITE...', 1, 'The password yo...') #6 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/core-command/src/Core_Command.php(618): wp_install('COMPANY', 'admin', 'USER@ADDRESS.....', true, '', 'FAKEPW') #7 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/core-command/src/Core_Command.php(401): Core_Command->do_install(Array) #8 [internal function]: Core_Command->install(Array, Array) #9 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func(Array, Array, Array) #10 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}(Array, Array) #11 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(491): call_user_func(Object(Closure), Array, Array) #12 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(399): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array) #13 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(422): WP_CLI\Runner->run_command(Array, Array) #14 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1214): WP_CLI\Runner->run_command_and_exit() #15 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runner->start() #16 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(77): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState)) #17 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap() #18 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('/usr/local/cpan...') #19 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/wpt-wp-cli.php(31): require_once('/usr/local/cpan...') #20 Command line code(1): require('/usr/local/cpan...') #21 {main} thrown in /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php on line 874 Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.
We have successfully updated existing WP installations using the WPTK, and haven't experienced these issues. We tried twice to install, failing both times with the same errors, public_html empty both times. Anybody have any idea what is going on?

Comments

29 comments

Date Votes
  • quietFinn
    0
  • jndawson
    Here:

     

    Yup, that was it.  Thanks.

    0
  • jndawson
    And now a new issue, apparently while trying to install the WP essentials/Jetpack plugins: Could not install the set on the WordPress website. Could not install the set on the WordPress website. - Unable to install plugin 'limit-login-attempts-reloaded' to 'WordPress instance #11 ('https://DOMAIN/wordpress')'. WP-CLI response: 'Fatal error: [snuffleupagus][disabled_function] Aborted execution on call of the function 'curl_setopt', because its argument '$option' content (81) matched the rule 'Please don't turn CURLOPT_SSL_VERIFYHOST off.' in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/rmccue/requests/library/Requests/Transport/cURL.php on line 152 Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website. ' - Fatal error: [snuffleupagus][disabled_function] Aborted execution on call of the function 'curl_setopt', because its argument '$option' content (81) matched the rule 'Please don't turn CURLOPT_SSL_VERIFYHOST off.' in /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/rmccue/requests/library/Requests/Transport/cURL.php on line 152 Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.
    Not sure what's going on, but we've had at least 2 other customers asking about this. It's difficult to encourage customers to maintain updated sites when they run into these issues.
    0
  • jndawson
    This link explains how to fix it, but the question is, will something else break? And why isn't it already fixed? PHP Fatal error: [snuffleupagus][disabled_function] Aborted execution on call of the function 'curl_setopt', because its argument '$option' content (81) matched the rule 'Please don't turn CURLOPT_SSL_VERIFYHOST off.' - Knowledgebase - Assistanz Networks Basically, find the file: /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/rmccue/requests/library/Requests/Transport/cURL.php Make the following changes: From ~~~ 152 curl_setopt($this->handle, CURLOPT_SSL_VERIFYHOST, 0); 153 curl_setopt($this->handle, CURLOPT_SSL_VERIFYPEER, 0); 161 curl_setopt($this->handle, CURLOPT_SSL_VERIFYHOST, 0); ~~~ To ~~~ 152 curl_setopt($this->handle, CURLOPT_SSL_VERIFYHOST, 1); 153 curl_setopt($this->handle, CURLOPT_SSL_VERIFYPEER, 1); 161 curl_setopt($this->handle, CURLOPT_SSL_VERIFYHOST, 1);
    ~~~
    0
  • cPRex Jurassic Moderator
    I was just about to link that workaround - glad you found it!
    0
  • jndawson
    I was just about to link that workaround - glad you found it!

    Why is the workaround needed? Most customers have no idea what the error means, or how to fix it, and NONE of them have the access to do it. Fix the code before it's released.
    0
  • cPRex Jurassic Moderator
    This workaround isn't something that's part of WordPress Toolkit. The workaround is something that gets applied to the WordPress theme itself if the site disables that specific PHP something. There just isn't a way to account for this on the cPanel side of things. I actually thought you had posted our article, but now realize that isn't the case. There are more details on this here:
    0
  • jndawson
    This workaround isn't something that's part of WordPress Toolkit. The workaround is something that gets applied to the WordPress theme itself if the site disables that specific PHP something. There just isn't a way to account for this on the cPanel side of things. I actually thought you had posted our article, but now realize that isn't the case. There are more details on this here:
    0
  • cPRex Jurassic Moderator
    @jndawson - sorry about the delay, but I wanted to reach out to some other team members and do some research on this. Unfortunately I don't think there is anything we can do on the cPanel side here. The issue happens with either a plugin or a custom theme where they are trying to disable the SSL verification. You mentioned the Curl file but our recommendation is to edit the value in the functions.php file for WordPress. Does an update also overwrite this file? WordPress themselves have been made aware of the issue, and also tagged this as "won't fix" because it's not an issue with the WordPress core tools. Details on that can be found here:
    0
  • jndawson
    [snip] You mentioned the Curl file but our recommendation is to edit the value in the functions.php file for WordPress. Does an update also overwrite this file? [snip]

    We've referred three customers to the referenced page and the collective response has been, "wtf?" The 2 biggest complaints are (1) the instructions don't say where the line is to be inserted into (2) which of the theme's 3 functions.php files. And I would imagine that every time a theme gets updated the functions.php file gets rewritten. So, between Wordpress, theme developers, and cPanel, there are no fixes that don't require training customers how to fix a known problem or tie up staff resources fixing somebody elses' code. On a personal note, I'm currently wrangling system and network updates in three data centers and really am a bit chuffed we have to deal with this, and will continue to have to deal with this.
    0
  • jndawson
    More update: We've added the line from
    0
  • cPRex Jurassic Moderator
    Can you open a ticket with our team so we can look into this on your system?
    0
  • jndawson
    Ticket #94430741
    0
  • cPRex Jurassic Moderator
    Thanks for that - it looks like we haven't been able to access the machine yet, but I'm following along with that ticket now.
    0
  • jndawson
    Thanks for that - it looks like we haven't been able to access the machine yet, but I'm following along with that ticket now.

    There seem to be issues with the support portal, but haven't heard anything back for a day or so.
    0
  • cPRex Jurassic Moderator
    I haven't heard of any issues with the ticket system. Our last reply was sent around 8PM last night.
    0
  • jndawson
    Just thought I'd point out that the IPs listed in WHM > Support > Grant cPanel Access...: Info: Make sure that the following IP addresses may connect to your server:
    • 184.94.197.6 - cPanel Support
    • 184.94.197.5 - cPanel Support
    • 184.94.197.4 - cPanel Support
    • 184.94.197.3 - cPanel Support
    • 208.74.123.98 - cPanel Support
    • 69.175.106.198 - Cloud Linux Support
    • 35.161.131.175 - LiteSpeed Web Server Support
    • 184.94.197.2 - cPanel Support
    ... don't include the 2 IPs the CP techs were trying to use to access our server: 208.74.121.38 & 159.253.142.50
    0
  • cPRex Jurassic Moderator
    I see you included that in the ticket too - we'll be sure to get that updated!
    0
  • jndawson
    I see you included that in the ticket too - we'll be sure to get that updated!

    We also have a bunch more IPs that we've whitelisted over the years based on lists provided by cPanel that aren't listed on the page. All this to say that we've opened numerous tickets in the past with zero issues.
    0
  • jndawson
    Update: After the system-related cURL.php file was over written during updates, we found the theme-related cURL.php files and edited those. We had typoed the cURL.php change in one place causing the intermittent 404s. After fixing it, no issues. In the meantime, we had tried the function.php fix with zero affect (effect?). So, again, between Wordpress, theme developers, and cPanel, there are no fixes that don't require training customers how to fix a known problem or tie up staff resources fixing somebody elses' code.
    0
  • cPRex Jurassic Moderator
    I did some additional research on this today in another thread. The short story is "its' experimental and may not work properly in all cases"
    0
  • jndawson
    I did some additional research on this today in another thread. The short story is "its' experimental and may not work properly in all cases"
    0
  • jndawson
    I have what may be a permanent fix for snuffleupagus errors beyond the 'curl_setopt' issue described above. After some more research, snuffy works better when the rule set is incorporated with php.ini files. References are: The result is to add the following to the php.ini file for php 7.4: [PHP] ; Snuffleupagus module=snuffleupagus.so sp.configuration_file=/opt/cpanel/ea-php74/root/etc/php.d/20-snuffleupagus.rules.d/*.rules,/usr/share/cagefs/.cpanel.multiphp/opt/cpanel/ea-php74/root/etc/php.d/20-snuffleupagus.rules.d/*.rules
    So far, our canaries haven't had an issue with it. This adds several functions that handle the vulnerabilities, for example: ##Prevent various `include`-related vulnerabilities sp.disable_function.function("require_once").value_r("\.(inc|phtml|php)$").allow(); sp.disable_function.function("include_once").value_r("\.(inc|phtml|php)$").allow(); sp.disable_function.function("require").value_r("\.(inc|phtml|php)$").allow(); sp.disable_function.function("include").value_r("\.(inc|phtml|php)$").allow(); sp.disable_function.function("require_once").drop() sp.disable_function.function("include_once").drop() sp.disable_function.function("require").drop() sp.disable_function.function("include").drop()
    If anybody has any thoughts, they would be welcome.
    0
  • jndawson
    I have what may be a permanent fix for snuffleupagus errors beyond the 'curl_setopt' issue described above. After some more research, snuffy works better when the rule set is incorporated with php.ini files.

    Nevermind. After testing with and without the rule set called in php.ini, we're still seeing unfortunate failures. In particular, WP updates are failing: Fatal error: [snuffleupagus][disabled_function] Aborted execution on call of the function 'require' in /home/USER/public_html/wp-includes/load.php on line 310
    Until the Wordpress people, the snuffleupagus developer, the php.net people, and the CloudLinux and cPanel people figure something out, we're removing snuffy from EA4 - it's not worth the staff resources trying to fix something that's unfixable. UPDATE: We removed the snuffy plugin and, voila, WP will update now.
    0
  • jndawson

    So, it seems we still have the issue that if you are using php8.x and the php mail() function is disabled (as it should be), then you'll get this:

    Fatal error: Uncaught Error: Call to undefined function PHPMailer\PHPMailer\mail() in /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php:880
Stack trace:
#0 /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php(1968): PHPMailer\PHPMailer\PHPMailer->mailPassthru()
#1 /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php(1691): PHPMailer\PHPMailer\PHPMailer->mailSend()
#2 /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php(1523): PHPMailer\PHPMailer\PHPMailer->postSend()
#3 /home/USER/public_html/wp-includes/pluggable.php(547): PHPMailer\PHPMailer\PHPMailer->send()
#4 /home/USER/public_html/wp-admin/includes/upgrade.php(644): wp_mail()
#5 /home/USER/public_html/wp-admin/includes/upgrade.php(141): wp_new_blog_notification()
#6 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/core-command/src/Core_Command.php(675): wp_install()
#7 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/core-command/src/Core_Command.php(437): Core_Command->do_install()
#8 [internal function]: Core_Command->install()
#9 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func()
#10 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}()
#11 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(497): call_user_func()
#12 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(441): WP_CLI\Dispatcher\Subcommand->invoke()
#13 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(464): WP_CLI\Runner->run_command()
#14 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1316): WP_CLI\Runner->run_command_and_exit()
#15 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#16 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(83): WP_CLI\Bootstrap\LaunchRunner->process()
#17 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap()
#18 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('/usr/local/cpan...')
#19 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/wpt-wp-cli.php(31): require_once('/usr/local/cpan...')
#20 Command line code(1): require('/usr/local/cpan...')
#21 {main}
  thrown in /home/USER/public_html/wp-includes/PHPMailer/PHPMailer.php on line 880
Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.
[error]FailedToExecuteWpCliCommand: exit status 1[/error]

    And we know this because https://support.cpanel.net/hc/en-us/articles/4406152233239-WP-Toolkit-fails-to-install-WordPress-when-site-is-set-to-PHP-8-and-the-mail-function-is-disabled  says so. We turned off the email notification option as suggested, so we're not having the issue anymore, but holy moly, people.

    It's been years; is anybody even pretending to look at this?

     

    0
  • cPRex Jurassic Moderator

    Hey hey.  No, no one is working on this currently on the cPanel side of things as that deflection article always resolves the issue.

    I did see that Plesk was able to resolve this issue recently so I don't see why we couldn't do the same on the cPanel side of things.  I've left some notes in case EXTWPTOOLK-8757 with more details for the developers to look at so it should get some action now.

    0
  • jndawson

    "...as that deflection article always resolves the issue."  Because of course. :D

     

     

    0
  • cPRex Jurassic Moderator

    I spoke with the WP Toolkit team and they do not plan to fix this issue because the mentioned workaround is in place.

    0
  • jndawson

    Imagine my response.

    1

Please sign in to leave a comment.

Didn't find what you were looking for?

New post