ERR blocked by Orb - 404 Error exclusively on Images using CDN

Hello everyone,

Permalink: https://67ac67208e989787697e136a–pixelsmarket.netlify.app/
Using DNS: https://pixels.market/

I have built a website using Next.js and Airtable.
I mostly use airtable to fetch data from whatever it’s texts or images.

The website was working well in the past few months. We are working on a new version, so we did not modify the code, neither touch any of the settings.

However, recently, we found out that no images can be load anymore on the website. It seems like all images are blocked from fetching. If you go on the website with the DNS (https://pixels.market/), you can see that all images are missing. But, if you use the permalink, the website works perfectly (https://67ac67208e989787697e136a–pixelsmarket.netlify.app/)

I tried multiples things such as:

  • Rebuilding the website completely without cache
  • Changing the sizes of the images
  • Fetching another images from airtable
  • Removing optimized images

With the last thing I did, I found out that when the website is fetching the images, I receive a response ERR_BLOCKED_BY_ORB with a 404 not found response. However, when I open the links that I have just tried to fetch in another tab, the images actually do exist.

I guess the problem is related to something close to a cors issue but I am not entirely certain where to investigate now.

Using this other post: 404 on Image load - #5 by luke
I manage to see that I get a 404 with my referer:

curl --compressed -svo /dev/null --stderr - 'https://v5.airtableusercontent.com/v3/u/38/38/1739361600000/mYAKvaquIzrl48JRzI8CCw/s2KG98qLE1iIBEjWTIdtVtkYjFuQlx5petU70IN_bY0xkYV2pUzl4pbY3lf5fSjoiUUNYI6uZFMUgdplmD8iTEE9Zuf1O5Pxa9BQYdHl82s1fBRiU_I8lcerkfYFtgYGhSzXhY2GuEntag-6HCTGBA/xu2VbMOIUZ0mGN6Lh5vFubfTIW3LuyD6IkrMGF9ffAo' -H 'referer: https://pixels.market' | egrep '^(<|>)'
> GET /v3/u/38/38/1739361600000/mYAKvaquIzrl48JRzI8CCw/s2KG98qLE1iIBEjWTIdtVtkYjFuQlx5petU70IN_bY0xkYV2pUzl4pbY3lf5fSjoiUUNYI6uZFMUgdplmD8iTEE9Zuf1O5Pxa9BQYdHl82s1fBRiU_I8lcerkfYFtgYGhSzXhY2GuEntag-6HCTGBA/xu2VbMOIUZ0mGN6Lh5vFubfTIW3LuyD6IkrMGF9ffAo HTTP/2
> Host: v5.airtableusercontent.com
> User-Agent: curl/8.5.0
> Accept: */*
> Accept-Encoding: deflate, gzip, br, zstd
> referer: https://pixels.market
> 
< HTTP/2 404 
< content-type: text/html
< content-length: 848
< last-modified: Mon, 18 Dec 2023 22:33:25 GMT
< x-amz-server-side-encryption: AES256
< x-amz-version-id: blDhLj8eVvIV4PXi30rMITR2JGdceYyw
< accept-ranges: bytes
< server: AmazonS3
< date: Tue, 11 Feb 2025 10:39:51 GMT
< etag: "59ce5e7acafd18e14b269964f867b6a3"
< vary: accept-encoding
< x-cache: LambdaGeneratedResponse from cloudfront
< via: 1.1 9a45d51617e0384dbdf52a8db118d3be.cloudfront.net (CloudFront)
< x-amz-cf-pop: CDG55-P3
< x-amz-cf-id: Q4kO5w9bs_yc0HjGAXvQHRRGnfdtdiz3gxopbGlpITGlq5qec5JRsg==
< age: 84918
< 

However in this case, I need to do hotlinking, so I am not sure what is my course of action here.
And also, why was it working before and suddently stop?

I’d imagine something has changed.

Since the response is being tailored on AirTable’s side premised on the referrer, it’s possible they changed their handling.

1 Like