Version 7.3 causes 504 timeout during plugin activation

  • fabiohemkemaier

    (@fabiohemkemaier)


    1 week, 3 days ago

    Hello,

    I am experiencing a critical issue with Tagembed Social Feeds Widget version 7.3.

    Environment:

    • WordPress 7.0
    • PHP 8.2.31 (CGI/FastCGI)
    • MariaDB 10.3.39
    • Elementor 4.1.4 / Elementor Pro 4.1.2
    • WP Super Cache 3.1.1

    Problem:

    As soon as I activate the Tagembed plugin, the WordPress admin becomes inaccessible and eventually returns a 504 Gateway Timeout error.

    Server logs show PHP/FastCGI requests timing out after 300 seconds:

    mod_fcgid: read data timeout in 300 seconds

    The website itself may continue to serve cached pages because WP Super Cache is enabled, but wp-admin becomes unusable.

    Troubleshooting already performed:

    • Renaming the plugins directory restores access to wp-admin.
    • Re-enabling all plugins except Tagembed works normally.
    • The issue occurs immediately when Tagembed is activated.
    • Deactivating Tagembed immediately resolves the problem.
    • No other plugin causes this behavior.

    Could you please advise:

    1. Are there any known issues with version 7.3 causing activation timeouts?
    2. Is there a way to disable the initial synchronization or remote API calls during activation?
    3. Is there a recommended version that is currently stable with WordPress 7.0 and PHP 8.2?

    Additional finding:

    The official website https://tagembed.com is currently returning ERR_NAME_NOT_RESOLVED from my network. This may explain why the plugin hangs during activation if it tries to contact Tagembed servers or APIs.

    Could the plugin activation process be waiting indefinitely for a remote request to Tagembed services?

    Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Raam Dev

    (@raamdev)

    1 week, 3 days ago

    The issue affects older versions too (e.g., v7.2). The problem is that the plugin attempts to connect to an API on tagembed.com and does not currently handle the scenario where the website is down, so the plugin generates an infinite loop that leads to out-of-memory issues.

    The infinite loop can be found on Lines 10-18 in helper/helper.php.

    Commenting out the following line in the tagembed.php prevents it from making the API call that is generating the infinite loop (line number 1623 in v7.2, or line 1625 in v7.3):

    add_action('in_admin_header', '___tagembed__hideGeneralAdminNotice');
    henmaker

    (@henmaker)

    1 week, 3 days ago

    It is not, it is because their services is down and domain name is not renew!
    https://who.is/whois/tagembed.com

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

You must be logged in to reply to this topic.