Cron-conversion running constantly

  • Resolved mattf10

    (@mattf10)


    3 months, 4 weeks ago

    My server logs are full of requests calling cron-conversion:

    "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1;

    But in the plugin admin dashboard, the number of images left to convert never changes, so it doesn’t appear the cron process is doing anything.

    In addition, the return code is ‘499’ = client closed connection.

    It’s likely all these requests are overloading the server. Is there a reason this cron job is running all the time but not doing anything?

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    3 months, 4 weeks ago

    Hi @mattf10,

    Thank you for your message.

    Please tell me, do you have the “Convert automatically images from custom directories” option activated in the “Advanced Settings” tab in the plugin settings panel?

    Best,
    Mateusz

    Thread Starter mattf10

    (@mattf10)

    3 months, 4 weeks ago

    Thanks for the quick reply.

    No, I don’t.

    If it helps, I have the plugin installed on a few other sites where I’m not seeing this behaviour. This one is a WooCommerce site, but so is one of the others. In other words, I can’t see any difference between this site and the others.

    Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    3 months, 4 weeks ago

    Thank you for the answer @mattf10!

    Please send me a screenshot of the “Bulk Optimization of Images” tab from the plugin settings panel.

    Thread Starter mattf10

    (@mattf10)

    3 months, 4 weeks ago

    Here you go.

    View post on imgur.com
    View post on imgur.com
    Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    3 months, 4 weeks ago

    @mattf10, thank you!

    Please convert all images so that 100% of the converted images are displayed and then test to see if the problem is resolved. If not, please come back to this thread and we’ll look for a solution.

    Thread Starter mattf10

    (@mattf10)

    3 months, 3 weeks ago

    I did that, but still see the cron calls in the site access logs like the ones below. 

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:08 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:09 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:09 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:10 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:11 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:12 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 200 31 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:38 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:39 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:40 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:41 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:41 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:42 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:43 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:44 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:45 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:45 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:46 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:47 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:48 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 499 0 "-" "WordPress/6.9.1; https://www.coolicebox.com"

    2a01:7e00::f03c:93ff:fefc:a085 - - [13/Feb/2026:13:48:48 +0000] "POST /wp-json/webp-converter/v1/cron-conversion HTTP/1.1" 200 31 "-" "WordPress/6.9.1; https://www.coolicebox.com"
    Thread Starter mattf10

    (@mattf10)

    3 months, 3 weeks ago

    I did that but still see the the calls to cron in the server logs. I posted them in another thread but it was blocked. There were around 15 or 20 in a row after I converted all images.

    Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    3 months, 3 weeks ago

    @mattf10, it seems that your site is constantly generating thumbnails during visits, or that some plugin/tool ​​is periodically generating new thumbnails or calling the wp_update_attachment_metadata or image_make_intermediate_size filters.

    Our plugin detects the above filters. When either of these filters is used, the plugin attempts to convert the image again asynchronously. That’s when you see these requests.

    By default, these filters are called when you add a new image to the Media Library and when thumbnails are generated. It’s likely that some code on your site is abusing these filters.`

    Thread Starter mattf10

    (@mattf10)

    3 months, 3 weeks ago

    I searched the site’s wp-content folder for those filters. The only plugin that has them in the codebase is WooCommerce. I use WooCommerce on other sites with that also uses your plugin and I don’t have the same issue.

    Can you think of any other explanation why this is happening but only on this one site?

    Thanks

    Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    3 months, 3 weeks ago

    @mattf10, unfortunately, I can’t blindly tell you what the source is. This requires a thorough code analysis and deep code search to understand what’s happening.

    I can only help you here – in this support forum, in accordance with this support forum’s rules. Therefore, my ability to help at this stage ends. I wrote what I could in my previous message. I hope you understand.

    Thread Starter mattf10

    (@mattf10)

    3 months, 3 weeks ago

    That’s fine – thanks for the help provided until now.

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

You must be logged in to reply to this topic.