Plugin auto-updates fail when cache enabled

  • Resolved Tim

    (@timstl)


    3 weeks, 4 days ago

    Hello,

    I’ve been having an issue where plugin auto-updates fail and are rolled back. This occurs on any site running WordPress 6.6+ and WP Super Cache (although all are on the same server).

    Disabling caching in the WP Super Cache settings fixes the issue and plugins update successfully.

    Here’s an example of the error I’m seeing:

    [03-Nov-2024 15:01:19 UTC] Upgrading plugin 'wordpress-seo'…
    [03-Nov-2024 15:01:21 UTC] Plugin 'wordpress-seo' has been upgraded.
    [03-Nov-2024 15:01:23 UTC] Scraping home page…
    [03-Nov-2024 15:01:24 UTC] Loopback request failed: cURL error 18: transfer closed with outstanding read data remaining
    [03-Nov-2024 15:01:25 UTC] The update for 'wordpress-seo' contained a fatal error. The previously installed version has been restored.

    So it appears that when WordPress checks for fatal errors after the plugin update, a CURL error occurs and the plugin is rolled back.

    Here’s an example of the log after disabling caching in the WP Super Cache settings:

    [03-Nov-2024 15:04:18 UTC] Upgrading plugin 'wordpress-seo'…
    [03-Nov-2024 15:04:22 UTC] Plugin 'wordpress-seo' has been upgraded.
    [03-Nov-2024 15:04:24 UTC] Scraping home page…
    [03-Nov-2024 15:04:24 UTC] '###### wp_scraping_result_start:b56ac8883338a6987fd6de15828e2ca6 ######
    true wp_scraping_result_end:b56ac8883338a6987fd6de15828e2ca6

    Is there a WP Super Cache setting that can be adjusted to fix this problem?

    Thanks,

    Tim

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Tim

    (@timstl)

    In case anyone else encounters this problem, I found two solutions that both worked for me:

    • Disable the “Compress pages so they’re served more quickly to visitors” setting
    • Alternatively, add wp_scrape_key= to the rejected URL strings. This seems like a better solution to me.

    I suppose disabling caching of URLs with GET parameters would also work, but I didn’t verify that.

    • This reply was modified 3 weeks, 3 days ago by Tim.

    Hi Tim, could you share your site URL, so we can take a look.

    wildoperation

    (@wildoperation)

    Hello,

    One example is https://wildoperation.com

    But I’ve already implemented the wp_scrape_key= fix mentioned above on all sites that I was having this problem with, including this one. Since then, no updates have failed.

    Thanks,

    Tim

    edit: Replied from the wrong account, so just wanted to note that I am the original creator of this thread.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.