Your R2 bucket does not exist (workers.api.error.bucket_not_found)
I've configured my R2 bindings through the settings > runtime page.
CF autocompleted my bucket, but, somehow my builds are now failing.
Even if I click on the bucket link in the portal it will redirect me to the bucket, then show 10 times: bucket not exists message before loading the bucket.
They are EU buckets (don't know if this might affect anything).
Even old successful builds retried are failing.
(last build: 6c0e1ee904ba36389d237fe7c8a4955f16e1a364)
Any ideas?
16 Replies
Hey Wouter, just tried to reproduce this on my end and wasn't able to. I did get a flaky error when trying to create an EU jurisdictioned R2 bucket, but I tried again and it created just fine. I was able to bind to it with my worker.
Can you see if this also happens with a new build, or is it just pre-existing workers?
Hey Will, thanks for taking the time to reproduce. It's Page deployment, i tried old builds / new commits. But not sure how to make it fully new?
Would it be ok to dm you a video?
Sure, not a problem!
Followup: found a bug in the UI causing the 404 for EU jurisdictions (but only for pages, workers seem ok). The error you're getting is likely due to the missing
jurisdictional option in r2_buckets in your toml:
https://developers.cloudflare.com/workers/wrangler/configuration/#r2-buckets
(super easy to miss!)Cloudflare Docs
Configuration | Cloudflare Workers docs
Use a
wrangler.toml configuration file to customize the development and deployment setup for your Worker project and other Developer Platform products.Thanks Will!
I'm not using the wrangler.toml though. It's still there for Miniflare local but I should remove it from the repository haha.
14:55:33.771 A wrangler.toml file was found but it does not appear to be valid. Did you mean to use wrangler.toml to configure Pages? If so, then make sure the file is valid and contains the pages_build_output_dir property. Skipping file and continuing.
So it's skipping the wrangler.toml, this is good. But besides the UI bug there might be another bug maybe then?
Followup: Can confirm it's jurisdictional related.
Created two new non-eu buckets and added them through the interface for my preview env and it deployed without problems.
Followup 2: I've removed the wrangler.toml from the repo to make sure it wasn't conflicting or anything.
Working build with non-eu buckets: febf95b5-e620-4b38-af58-6c2e529925fa
Broken build with eu-buckets: ddbab73c-f46f-4931-9331-2c3a001e7c25@Walshy | Deploying (sorry for the tag, but see ya online ;)) still seeing the same jurisdictional failures on CI builds. Maybe this is an issue with pnpm?
added within UI?
OH. you know what though. Can't add through the UI that's not in yet lol.
Got a little ahead of myself 😅
So yeah even if Wouter removed and re-added through the UI, it's not going to get picked up yet.
yup
we got a fix in for that right? just not released yet or?
1/2 reviews 😅
will get that merged in before cut off today
You guys are awesome 😄 I'm not in a rush btw, so no problem if it's merged later
pr merged 🙂
will be released in a couple hours
Released 🙂 You should be able to remove and re-add the binding, and be back in action!
Woohoo!
Thanks both!