WP-OPTIMIZE KILLED ALL MY WEBSITES

  • Resolved rick7653

    (@rick7653)


    10 months, 3 weeks ago

    All of a sudden I could not load 12 of my different clients web pages. I was getting the message server is temporarily unable to handle a request: There is a high number of requests being sent to the server, exhausting all the available resources. The server is experiencing technical issues or maintenance work. I started disabling plugins and it turned out to be wp-optimize killing the pages. I deleted the plugin on all the websites now all pages work. This happened suddenly. The last up date I did was my theme files called NIRVANA and YES I have the latest version of wp-optimize. I installed an older version and it works fine. The problem is in the new 3.2.22 updated version

    • This topic was modified 10 months, 3 weeks ago by rick7653.
    • This topic was modified 10 months, 3 weeks ago by rick7653.
    • This topic was modified 10 months, 3 weeks ago by rick7653.
    • This topic was modified 10 months, 3 weeks ago by rick7653.
Viewing 2 replies - 31 through 32 (of 32 total)
  • Plugin Support wpmansour

    (@wpmansour)

    @iscomputerman, high PHP-FPM usage could be caused by excessive caching or database operations. You might want to try reducing the cache lifespan or disabling certain features like minification to ease the server load.

    @jakezehn, your approach of manually clearing the cache directory and setting a smaller cache window is a solid solution. Reducing the cache lifespan to ensure regular purges is key for avoiding the cache growing too large.

    For both of you, if the issues persist, consider adjusting the cache settings or disabling unnecessary features temporarily to balance server load. Feel free to start a new thread if you need more specific guidance!

    Florent

    (@flowebpro)

    In my previous message, I mentionned that the cache preloader was calling URL too many times. It’s the reason we get high php-fpm usage. In our case, the preloader call every URL more than 10 times !

    Support (@vupdraft?) answered that it was because of the “user specific” cache function. But It’s a premium function, we don’t use this function.

    So the preloader generate 10X more request that it should makes.

    172.71.102.188 - - [13/Nov/2024:17:02:09 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"
    172.71.118.215 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"
    172.71.127.111 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"
    172.71.183.58 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"
    172.71.127.26 - - [13/Nov/2024:17:02:09 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"
    172.71.127.26 - - [13/Nov/2024:17:02:09 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"
    172.71.119.23 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"
    172.71.99.34 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32378 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"
    172.69.223.181 - - [13/Nov/2024:17:02:07 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"
    172.71.118.186 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"
    172.70.46.109 - - [13/Nov/2024:17:02:11 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32404 "-" "Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"
    172.71.130.143 - - [13/Nov/2024:17:02:09 +0100] "GET /product-category/corsets/corset-skirts/ HTTP/1.1" 200 32709 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36"




    • This reply was modified 1 week, 1 day ago by Florent.
Viewing 2 replies - 31 through 32 (of 32 total)
  • You must be logged in to reply to this topic.