8 Replies
@switz do you have any of these environment variables set, in an env file or as actual environment variables? https://developers.cloudflare.com/workers/wrangler/system-environment-variables/#supported-environment-variables
Cloudflare Docs
System environment variables
Local environment variables that can change Wrangler's behavior.
yeah I have CLOUDFLARE_ACCOUNT_ID
Can you post the ACCOUNT_ID from the variable here? It is safe to share publicly
76935225f2967a3ddadf806d1bd9ba46
I'm stumped
this is frustrating tbhThe team is looking at it
thanks
any updates here? this is blocking my deployment of software running on d1
I think i found the issue
its trying to use the wrong cloudflare account - i cleared the ~/.wrangler directory and its still breaking
I figured it out
my
fish
shell export CLOUDFLARE_ACCOUNT_ID
was overwriting the local .env
if wrangler sees two different account ids it should warn you and suggest a possible fix (check bash_profile/env vars)
yeah that fixed it@switz thanks for the ping here š appreciate it!
I don't have the
CLOUDFLARE_ACCOUNT_ID
exported in the env, and I have it defined in the wrangler.toml. What is weird is that I receive an authentication error, but it says that I have superuser access:
same issue and setup here - wrangler d1 execute is working but not list