Problem with Cloudflare Worker Image on specific datacenter CPH. AMS and FRA is working fine

Hi

We are starting to have problems with our Cloudflare worker which we are using to resize images.
The problem started for 6-7 hours ago.

It depends on which Cloudflare data center the clients connects to (CF-ray).

  let imageURL = "https://xxx.blob.core.windows.net/images/test.jpg";

  let options = { cf: {
    image: {}
  }}

  options.cf.image.height = 500
  options.cf.image.width = 500


  return fetch(imageURL, options)

The above code will fail on the following data centers
-LUX
-CPH
-FRA

The response will return a:
ERROR 9408: Could not fetch the image — the server returned HTTP error 400 Bad Request

On most Cloudflare data center the code still works
Like:
-AMS
-MIA

The last change we did on the Cloudflare JavaScript worker was over 2 months ago.
The images are located on a public Azure Blog storage.

So apparently it depends on which Cloudflare data center the Cloudflare is running on.

Am I the only who has discovered this?

1 Like

Hi, we have same issue. People from Scandinavia see same error but not me from CE. Maybe we can force worker to use specific datacenter.

1 Like

I have recorded a video showcasing the error

In the video I have created a super simple new worker

1 Like

Please let me know if you figure that out. (I haven’t found the option yet)

2 Likes

Based on Azure support looks like some datacenters where workers are executing call http instead of https. No more info yet.

1 Like

Yes it seems to relate to Azure Blob Storage.

I have created a AWS S3 storage and uploaded a image


And created a new worker using the AWS S3 and that is working fine, no matter which Cloudflare data center is used

NB I tried to switch from Azure Blob in West Europe to US and that did not change anything

We resolved the issue by disabling the Require secure transfer in the Azure storage configuration.

3 Likes

OMG I just discovered the same thing!

1 Like

Same here.

I faced same problem. I use Azure Storage Blob and Cloudflare Image Resizing through Workers.

The worker was able to get binary from Azure Storage Blob without cf resize otions.
It confused me. Just Image Resizer has be wrong.

Then, I found this thread and I tried this and It has got work.

We resolved the issue by disabling the Require secure transfer in the Azure storage configuration.

I hope Cloudflare team report the reason to use http between Azure Storage Blob and their Image Resizing.

1 Like

For reference I have this ticket number 3010625 on Cloudflare support

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.

Hi Team,

Can you tell me if you still face the trouble.
I have tickets 3010181 and 3010625 escalated with Engineering.

If the problem still persists, more tickets will be helpful.
I’ll close this topic if the issue has been resolved.

Thank you.

c09abeaae50b2b922e18a3ee47ba427c

1 Like

It seems to have been resolved.

This is how I tested:

  1. Enabled the Require secure transfer in the Azure storage configuration.
  2. Used VPN to test different data centers
  3. FRA & LUX did not work before. They are working now.

Data centers checked today
AMS
CDG
FRA - Did not work before. Is working now
FRA
HAM
HEL
LHR
LUX - Did not work before. Is working now
PRG
VNO
WAW

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.