• Resolved vasilisweb

    (@vasilisweb)


    Greetings,

    After updating the plugin, I started receiving a 500 error on the /wp-admin area, while all other pages on the site continue to function normally.

    When I temporarily deactivated the plugin, the /wp-admin dashboard loaded without issues. However, once I reactivated the plugin, the 500 error returned. The debug log does not report any related errors.

    Please advise on how to proceed.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support MM Aurangajeb

    (@aurangajeb)

    Hi @vasilisweb ,

    Thanks for reaching out.

    I’m sorry to hear you’re running into a 500 error after the update. I understand how frustrating it is to lose access to your dashboard, but we’ll certainly help you get this sorted out.

    Since the issue is isolated to the /wp-admin area and resolves when AIOSEO is deactivated, this often points to either PHP memory exhaustion or a conflict with another active plugin.

    You mentioned the debug log is empty. Because a 500 error is a fatal server error, the crash can happen so quickly (often due to running out of memory) that WordPress doesn’t have time to write the error to the debug.log file.

    Please try the following steps to troubleshoot:

    1. Increase PHP Memory Limit:
      This is the most common cause for backend crashes after an update. Please try increasing your WordPress memory limit to ensure the server has enough resources. You can do this by adding the following line to your wp-config.php file, right before the line that says “That's all, stop editing“:

    define( 'WP_MEMORY_LIMIT', '512M' );or above.

    1. Check Server-Level Logs:
      If increasing the memory doesn’t work, please check if the error is recorded in your server’s main Apache or Nginx error log. If you’re unsure where to find this, your hosting provider can locate it for you. This log is crucial, as it will show the specific fatal error causing the crash.

    Also, please double-check that you’ve followed the standard method to check the debug.log, as outlined here: https://aioseo.com/docs/how-to-enable-debugging-in-wordpress/

    Please let me know if increasing the memory resolves the issue or if you are able to retrieve an error message from the server logs.

    I’m looking forward to hearing from you!

    Thread Starter vasilisweb

    (@vasilisweb)

    It turned out that it wasn’t a PHP Memory issue. Instead, it was a database-related problem: the system was attempting to write a transient to the wp_options table, but this failed due to the max_allowed_packet limit, compounded by constraints introduced by another plugin.

    Sorry for the inconvenience and thank you for your support.

    Plugin Support MM Aurangajeb

    (@aurangajeb)

    Hi @vasilisweb,

    I appreciate your update and follow-up. I’m happy to hear that your website’s problem has been fixed!

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.