• Resolved nicola1013

    (@nicola1013)


    Hello. A few minutes after I updated to the latest version this evening (Jan. 26, 2021), encountered this fatal error (and the site’s php memory has long been at 256mb, so that’s not the issue).

    Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 137438953444 bytes) in /home/customer/www/xxxxxxxx.com/public_html/wp-content/plugins/wordpress-seo/wp-seo-main.php on line 56

    This error made the entire website inaccessible. I’m pretty sure it’s the Yoast plugin because once I deactivated it, the site was able to load as normal.

    I’m guessing there’s a conflict somewhere. I’ve removed the plugin for now, but do hope the specific problem is identified and there’s another update.

    If you insist that it’s not the Yoast plugin, I guess I’ll look elsewhere for what could have suddenly caused this issue. However, I am a News SEO user so some good advice would be helpful.

    Thank you.

    • This topic was modified 4 years, 1 month ago by nicola1013.
Viewing 2 replies - 1 through 2 (of 2 total)
  • @nicola1013

    We understand that when you have Yoast SEO plugin active you get a message that you are out of memory. Yoast requires a certain amount of PHP memory in order to run and sometimes other plugins are also using PHP memory. If the site does not have enough memory running along with other plugins you get those errors. We suspect not having enough memory is the issue.

    We also want to say that the host provider controls how much memory is available. We ask that you please review the memory and confirm with us the three points below:

    1. Is your PHP memory at a minimum of 256M?

    2. If it is, please double it. Your host provider can help with this.

    3. If doubling fails to work, please triple it.

    Let us know if that resolves the issue.

    Just for your info, if the issue happens with Yoast News SEO premium plugin, please contact our support team directly.

    Thread Starter nicola1013

    (@nicola1013)

    The issue has resolved itself, it seems. Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Fatal error in Latest Update’ is closed to new replies.