Delivery check fails
The delivery check loads a small test image from your public address, as a visitor's browser would. If it fails, the address doesn't lead to a public copy of your file yet. Your site keeps loading images from your server meanwhile. The message tells you which part to fix.
"We couldn't find [domain]."
Check the domain setup at your DNS provider. The domain needs a DNS record that points to your storage or CDN. If you added it just now, wait a few minutes and test again.
"[domain] doesn't have a working HTTPS certificate yet."
If you connected the domain just now, its certificate can take a few minutes. Test again soon. Otherwise, check the domain's SSL settings.
"[domain] refused to show the test file."
The bucket isn't public yet:
- Cloudflare R2: connect the domain in R2 → your bucket → Settings, or turn on the r2.dev public URL for testing.
- Amazon S3: turn off Block Public Access for this bucket and add a bucket policy that allows
s3:GetObjecton its files. - Backblaze B2: set Files in Bucket to Public.
- MinIO: allow anonymous downloads, for example with
mc anonymous set download. - Others: make the bucket, or its files, publicly readable.
"The test file wasn't found at [domain]."
The address doesn't lead to this bucket. Check that the domain or CDN is connected to the right one.
"[domain] redirects to another address."
Use the final address, the one it redirects to, as your delivery address.
"Browsers block http images on https pages."
Use the https:// version of your delivery address. If it doesn't load, turn on HTTPS for that domain first.
"A different file came back."
The address may lead to another bucket or website, or a CDN may be changing images. Check that it serves your bucket unchanged.
"Images load, but web fonts and scripts ... cannot read files."
This is a CORS note, and images on your pages still work. You only need a CORS rule if you offload fonts, or a theme or plugin loads media with scripts. Each setup guide has an optional CORS step.