Image pull process failure: Failed to pull image

did it give any image link alone with that curl error 28 ?

if so , can you open that image link in your own browser?

The list was too long…
But, I did try to access some if the URL’s directly and that always resulted in a 404.
I’ve had long chats with my provider and there are no issues on that end.
On the QUIC.cloud dashboard, I’ve switched Bypass CDN On, and that appears to help, but I am not sure that anything is being cached right now. To be honest, I am spending way too much time getting all the quic processes to work. (no offense)

I know that cURL is very difficult to troubleshoot, but I am starting to suspect QUIC’s DNS performance. Right now, I lack the time to dive into that deeper though. I may decide to do a roll-back tonight and stop using their CDN, but I first want to be sure what the effect of that will be on the webp process. As I said in another thread, the documentation is rather unclear at times.

Thanks for looking into this!

• This reply was modified 9 months, 1 week ago by Blamedutchie. Reason: clarification
• This reply was modified 9 months, 1 week ago by Blamedutchie.

no, this has nothing to do with CDN

the pull process was your site/server <-> image optm server , CDN is not involved in image optm process

there are 2 side of issue , 1) is the image optm server are busy and under heavy load, when this happens, the plugin tries to download optimized image back from image server will hit time out due to heavy load , on such case, just try again later on , it’d usually start to work normally.

2) the site was not able to connect to the image optm server , this could be various reason , a sensitive or restricted security measures , a temp network issue between your server and image server , a misconfiguration on PHP or server …etc

if you can reproduce the issue, please try this , edit file /wp-content/plugins/src/img-optm.cls.php , around line 1036, you will see if (empty($response->success)) {

add this before this if line

error_log( print_r($response, true) ,3 , '/path/to/your/site/lscwp1.log' );

then at line 1173, you will see $wp_response = wp_remote_get($req['url']

add this code after that line

error_log( print_r($wp_response, true) ,3 , '/path/to/your/site/lscwp2.log' );

then try to trigger the issue again , the lscwp1.log or lscwp2.log file , should give more detail about the error message

Hi @qtwrk

Thanks for being on top of this.
I’ve added the lines and ran a few tests.
Everything worked well and as intended, meaning that both optimization and pulling went without errors.

I know, theoretically, the CDN has nothing to do with these processes.
However, I was experiencing several issues that all disappeared after disabling the QUIC.cloud CDN, even though all signs were green. For me it is clear that something is not working as it should on that end.

The cURL error 28 still pops up every once in a while, but not necessarily related to this image processing. I know that already for many a year, many people using WordPress have that error and discussions on the topic are ongoing on various levels.

So, for now… Let’s consider this issue resolved.

Thanks!