• Resolved acostela

    (@acostela)


    Hello

    I have been having several website crashes today and yesterday until I realised that the issue was triggered after updating Yoast SEO to the latest version. See below main info as requested by @monbauza for other user with the same issue.

    – I am using WordPress 5.8 and Yoast SEO Version 16.8
    Details of any Yoast-related errors that appear in the server’s log
    – I was updating from 16.8 to 16.9
    – The issue occurred as soon as the plugin is updated, the website crashes and all I can see is a blank page not even a error page.
    – Website is currently on PHP 7.4

    Do yo have any suggestions?

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Md Mazedul Islam Khan

    (@mazedulislamkhan)

    Thanks for sharing all the relevant information here with us. We are sorry to hear that you’re having trouble with your website during the Yoast SEO plugin update process.

    Do you have the server error log with you? If yes, can you please share that here with us as well so that we can see whether is there something specific to our plugin?

    In addition, can you please confirm whether do you see any errors during the plugin update process?

    We look forward to hearing from you.

    Thread Starter acostela

    (@acostela)

    Hi see below the server error log.

    I don’t get to see any errors on screen when manually updating the plugin.

    [12-Aug-2021 00:17:19 UTC] PHP Warning: set_time_limit() has been disabled for security reasons in /usr/home/liverpoolbidcompany.com/web/wp-admin/includes/class-wp-upgrader.php on line 471
    [12-Aug-2021 00:17:23 UTC] PHP Warning: set_time_limit() has been disabled for security reasons in /usr/home/liverpoolbidcompany.com/web/wp-admin/includes/class-wp-upgrader.php on line 471
    [12-Aug-2021 00:17:25 UTC] PHP Warning: set_time_limit() has been disabled for security reasons in /usr/home/liverpoolbidcompany.com/web/wp-admin/includes/class-wp-upgrader.php on line 471
    [12-Aug-2021 02:20:14 Europe/Madrid] PHP Fatal error: Uncaught Error: Failed opening required ‘/home/liverpoolbidcompany.com/web/wp-content/plugins/wordpress-seo/wp-seo-ls.php’ (include_path=’.:’) in /usr/home/liverpoolbidcompany.com/web/wp-load.php:20
    Stack trace:
    #0 /usr/home/liverpoolbidcompany.com/web/wp-blog-header.php(13): require_once()
    #1 /usr/home/liverpoolbidcompany.com/web/index.php(17): require(‘/usr/home/liver…’)
    #2 {main}
    thrown in /usr/home/liverpoolbidcompany.com/web/wp-load.php on line 20
    [12-Aug-2021 02:20:23 Europe/Madrid] PHP Fatal error: Uncaught Error: Failed opening required ‘/home/liverpoolbidcompany.com/web/wp-content/plugins/wordpress-seo/wp-seo-ls.php’ (include_path=’.:’) in /usr/home/liverpoolbidcompany.com/web/wp-load.php:20
    Stack trace:
    #0 /usr/home/liverpoolbidcompany.com/web/wp-admin/admin.php(34): require_once()
    #1 /usr/home/liverpoolbidcompany.com/web/wp-admin/update-core.php(10): require_once(‘/usr/home/liver…’)
    #2 {main}
    thrown in /usr/home/liverpoolbidcompany.com/web/wp-load.php on line 20
    [12-Aug-2021 02:20:23 Europe/Madrid] PHP Fatal error: Uncaught Error: Failed opening required ‘/home/liverpoolbidcompany.com/web/wp-content/plugins/wordpress-seo/wp-seo-ls.php’ (include_path=’.:’) in /usr/home/liverpoolbidcompany.com/web/wp-load.php:20
    Stack trace:
    #0 /usr/home/liverpoolbidcompany.com/web/wp-blog-header.php(13): require_once()
    #1 /usr/home/liverpoolbidcompany.com/web/index.php(17): require(‘/usr/home/liver…’)
    #2 {main}
    thrown in /usr/home/liverpoolbidcompany.com/web/wp-load.php on line 20
    [12-Aug-2021 02:20:29 Europe/Madrid] PHP Fatal error: Uncaught Error: Failed opening required ‘/home/liverpoolbidcompany.com/web/wp-content/plugins/wordpress-seo/wp-seo-ls.php’ (include_path=’.:’) in /usr/home/liverpoolbidcompany.com/web/wp-load.php:20
    Stack trace:
    #0 /usr/home/liverpoolbidcompany.com/web/wp-blog-header.php(13): require_once()
    #1 /usr/home/liverpoolbidcompany.com/web/index.php(17): require(‘/usr/home/liver…’)
    #2 {main}
    thrown in /usr/home/liverpoolbidcompany.com/web/wp-load.php on line 20
    [12-Aug-2021 02:13:58 UTC] PHP Fatal error: Allowed memory size of 335544320 bytes exhausted (tried to allocate 20480 bytes) in /usr/home/liverpoolbidcompany.com/web/wp-includes/meta.php on line 1085
    [12-Aug-2021 02:13:58 UTC] PHP Fatal error: Allowed memory size of 335544320 bytes exhausted (tried to allocate 1093632 bytes) in /usr/home/liverpoolbidcompany.com/web/wp-includes/functions.php on line 4979
    [12-Aug-2021 02:13:58 UTC] PHP Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0
    [12-Aug-2021 02:55:32 UTC] PHP Fatal error: Allowed memory size of 335544320 bytes exhausted (tried to allocate 20480 bytes) in /usr/home/liverpoolbidcompany.com/web/wp-includes/meta.php on line 1085
    [12-Aug-2021 02:55:32 UTC] PHP Fatal error: Allowed memory size of 335544320 bytes exhausted (tried to allocate 1093632 bytes) in /usr/home/liverpoolbidcompany.com/web/wp-includes/functions.php on line 4979
    [12-Aug-2021 02:55:32 UTC] PHP Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0
    [12-Aug-2021 02:55:57 UTC] PHP Fatal error: Allowed memory size of 335544320 bytes exhausted (tried to allocate 20480 bytes) in /usr/home/liverpoolbidcompany.com/web/wp-includes/meta.php on line 1085
    [12-Aug-2021 02:55:57 UTC] PHP Fatal error: Allowed memory size of 335544320 bytes exhausted (tried to allocate 1093632 bytes) in /usr/home/liverpoolbidcompany.com/web/wp-includes/functions.php on line 4979
    [12-Aug-2021 02:55:57 UTC] PHP Fatal error: Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0

    To add to this, our website also produced fatal errors when updating to the latest version. We had to roll back to the old versions to recover the site.

    Plugin Support Maybellyne

    (@maybellyne)

    Thanks for sharing the error log @acostela. The errors related to Yoast SEO seem to be related to when a server runs out of memory to complete the task at hand.

    To solve this problem, please reach out to your web hosting provider to increase the amount of memory available to your WordPress installation. You can see instructions for that here: https://yoast.com/help/common-installation-update-errors/#memory-exhausted

    @acostela What you should do to solve the problem is to go back to the previous version of Yoast or to go back to an old version of PHP. I decided to stop using Yoast, because this already happened to me in the last two Yoast updates. Even my hosting (siteground) already knew that the problem was caused by Yoast when I went to them because my site was down.

    @baemosse Going back to an older version of PHP also fixes the problem, but is not ideal.

    Thread Starter acostela

    (@acostela)

    Thanks @maybellyne

    I have asked my hosting provider to update those. Fingers crossed it works.

    Cheers

    Thread Starter acostela

    (@acostela)

    Hi @maybellyne

    The hosting provider did those amends around memory and upgraded to PHP 8 and got the error below when trying to update the plugin:

    Fatal error: Uncaught Error: Failed opening required ‘/home/liverpoolbidcompany.com/web/wp-content/plugins/wordpress-seo/wp-seo-ls.php’ (include_path=’.:’) in /usr/home/liverpoolbidcompany.com/web/wp-load.php:20 Stack trace: #0 /usr/home/liverpoolbidcompany.com/web/wp-blog-header.php(13): require_once() #1 /usr/home/liverpoolbidcompany.com/web/index.php(17): require(‘/usr/home/liver…’) #2 {main} thrown in /usr/home/liverpoolbidcompany.com/web/wp-load.php on line 20

    Apparently a file was being removed with the update, which they managed to restore and now everything is working fine.

    @baemosse you might want to try all of the above to fix your issue.

    I am posting the full process to fix the issue we had just in case this helps other people.

    Cheers

    Thread Starter acostela

    (@acostela)

    This is now fixed

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Website crash after updating plugin’ is closed to new replies.