Does `CLOUDFLARE_ACCOUNT_ID` work?

HHard@Work Does `CLOUDFLARE_ACCOUNT_ID` work?

B

Brett Willis•6/2/25, 9:29 PM

Looks like it works, was looking for CLI arguments not env variables so thanks for pointing it out!

O

Oz•6/3/25, 12:13 AM

Any idea on the timeline for worker aliases? (Like Pages aliases, branch name = url prefix)

A

Abrahem•6/3/25, 2:01 AM

:this:

<

<@235148962103951360>•6/3/25, 2:59 AM

is there a way to run multiple workers together with different routes locally with wrangler?

�

💀WOMBOVERSE💀•6/3/25, 4:11 AM

G

grrowl•6/3/25, 10:05 AM

Why not deploy to prod if that’s what you want

K

KelvTan•6/3/25, 11:43 AM

Thanks

J

James•6/3/25, 12:34 PM

One I forgot to raise yesterday during office hours @petebd, but are the daily workers-types releases even without any changes intentional?

OOz Any idea on the timeline for worker aliases? (Like Pages aliases, branch name = ...

P

petebd•6/3/25, 12:47 PM

This quarter

A

ALECKS•6/3/25, 6:03 PM

I have a worker that I run through the vite plugin, so locally with

vite dev

vite dev

vite dev

vite dev. The problem is that this worker is a "child" binding in a parent router, and when it starts up, the parent

wrangler dev

wrangler dev

does not see it. Is there any way to get this working?

EEdmund Hung Do you mean the worker running in wrangler dev has a service binding to another ...

A

ALECKS•6/3/25, 6:48 PM

Yes, that's the use case. I did have the latest plugin, 1.4.0, and it's not working. My top level wrangler:

{
  "name": "router",
  "main": "apps/dev-router/src/index.ts",
  "compatibility_date": "2025-04-03",
  "workers": {
    "dash": "apps/dash/wrangler.jsonc",
    "api": "apps/server/wrangler.jsonc"
  },

  "services": [
    {
      "binding": "DASHBOARD_SERVICE",
      "service": "dash"
    },
    {
      "binding": "API_SERVICE",
      "service": "api"
    }
  ],

  "dev": {
    "port": 8080,
    "local_protocol": "http"
  }
}

{
  "name": "router",
  "main": "apps/dev-router/src/index.ts",
  "compatibility_date": "2025-04-03",
  "workers": {
    "dash": "apps/dash/wrangler.jsonc",
    "api": "apps/server/wrangler.jsonc"
  },

  "services": [
    {
      "binding": "DASHBOARD_SERVICE",
      "service": "dash"
    },
    {
      "binding": "API_SERVICE",
      "service": "api"
    }
  ],

  "dev": {
    "port": 8080,
    "local_protocol": "http"
  }
}

{
  "name": "router",
  "main": "apps/dev-router/src/index.ts",
  "compatibility_date": "2025-04-03",
  "workers": {
    "dash": "apps/dash/wrangler.jsonc",
    "api": "apps/server/wrangler.jsonc"
  },

  "services": [
    {
      "binding": "DASHBOARD_SERVICE",
      "service": "dash"
    },
    {
      "binding": "API_SERVICE",
      "service": "api"
    }
  ],

  "dev": {
    "port": 8080,
    "local_protocol": "http"
  }
}

{
  "name": "router",
  "main": "apps/dev-router/src/index.ts",
  "compatibility_date": "2025-04-03",
  "workers": {
    "dash": "apps/dash/wrangler.jsonc",
    "api": "apps/server/wrangler.jsonc"
  },

  "services": [
    {
      "binding": "DASHBOARD_SERVICE",
      "service": "dash"
    },
    {
      "binding": "API_SERVICE",
      "service": "api"
    }
  ],

  "dev": {
    "port": 8080,
    "local_protocol": "http"
  }
}

it routes to either service. the api service shows up just fine, but not the dashboard, which I run with vite dev

A

ALECKS•6/3/25, 6:48 PM

A

ALECKS•6/3/25, 6:52 PM

no, it's a monorepo, each in their own workspace

�

💀WOMBOVERSE💀•6/3/25, 11:15 PM

�

💀WOMBOVERSE💀•6/3/25, 11:15 PM

Hello all

0

0x146231489231923•6/4/25, 6:33 AM

anyone knows how to list all workers? not only current project

C

cosbgn•6/4/25, 7:38 AM

On an mac running Monterey I can't start an app on the most recent wrangler version:

 ERROR  dyld[87080]: Symbol not found: (__ZNSt3__122__libcpp_verbose_abortEPKcz)


 ERROR    Referenced from: '/Users/x/dev/app/node_modules/@cloudflare/workerd-darwin-64/bin/workerd'
 ERROR    Expected in: '/usr/lib/libc++.1.dylib'
 ERROR  Failed to initialize wrangler bindings proxy write EPIPE

 ERROR  dyld[87080]: Symbol not found: (__ZNSt3__122__libcpp_verbose_abortEPKcz)


 ERROR    Referenced from: '/Users/x/dev/app/node_modules/@cloudflare/workerd-darwin-64/bin/workerd'
 ERROR    Expected in: '/usr/lib/libc++.1.dylib'
 ERROR  Failed to initialize wrangler bindings proxy write EPIPE

 ERROR  dyld[87080]: Symbol not found: (__ZNSt3__122__libcpp_verbose_abortEPKcz)


 ERROR    Referenced from: '/Users/x/dev/app/node_modules/@cloudflare/workerd-darwin-64/bin/workerd'
 ERROR    Expected in: '/usr/lib/libc++.1.dylib'
 ERROR  Failed to initialize wrangler bindings proxy write EPIPE

 ERROR  dyld[87080]: Symbol not found: (__ZNSt3__122__libcpp_verbose_abortEPKcz)


 ERROR    Referenced from: '/Users/x/dev/app/node_modules/@cloudflare/workerd-darwin-64/bin/workerd'
 ERROR    Expected in: '/usr/lib/libc++.1.dylib'
 ERROR  Failed to initialize wrangler bindings proxy write EPIPE

C

cosbgn•6/4/25, 7:39 AM

It worked till last week's version. Is this a bug or wrangler dropped support for Monterey?

C

cosbgn•6/4/25, 7:45 AM

Wrangler@4.16 seems to be the last version which doesn't throw this error

T

top kek•6/4/25, 3:15 PM

it says here that we can create secrets with the

-e

-e

-e

-e flag (it’s even mispelled) but it does not work, it instead tried to create a new worker with the name

<APP>-staging

<APP>-staging

<APP>-staging

<APP>-staging which has no bindings no nothing

T

top kek•6/4/25, 3:16 PM

how do you guys have different API keys for different environments? i just want my branches to have a different API key for a third party and it’s literally impossible with secrets lol

E

elVengador•6/4/25, 11:32 PM

Hello there, I have ad doubt regarding github actions and wrangler, I want to set some secrests, following the documentation I'm using:

secrets

secrets

secrets

secrets but it is not working, it returns an error

🔑 Uploading secrets...
  /usr/local/bin/npx wrangler secret bulk
  
   ⛅️ wrangler 4.18.0 (update available 4.19.1)
  ─────────────────────────────────────────────
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in your Wrangler configuration file, or pass it as an argument with `--name <worker-name>`

🔑 Uploading secrets...
  /usr/local/bin/npx wrangler secret bulk
  
   ⛅️ wrangler 4.18.0 (update available 4.19.1)
  ─────────────────────────────────────────────
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in your Wrangler configuration file, or pass it as an argument with `--name <worker-name>`

🔑 Uploading secrets...
  /usr/local/bin/npx wrangler secret bulk
  
   ⛅️ wrangler 4.18.0 (update available 4.19.1)
  ─────────────────────────────────────────────
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in your Wrangler configuration file, or pass it as an argument with `--name <worker-name>`

🔑 Uploading secrets...
  /usr/local/bin/npx wrangler secret bulk
  
   ⛅️ wrangler 4.18.0 (update available 4.19.1)
  ─────────────────────────────────────────────
  ✘ [ERROR] Required Worker name missing. Please specify the Worker name in your Wrangler configuration file, or pass it as an argument with `--name <worker-name>`

I coudn't find in the documentation where should I add --name into my github actions, I think if I'm using

cloudflare/wrangler-action@v3

cloudflare/wrangler-action@v3

cloudflare/wrangler-action@v3

cloudflare/wrangler-action@v3, is not required to create a .toml file, I've tried to set-up

--project-name

--project-name

--project-name

--project-name and

--name

--name

--name

--name but I couldn't solve it, how can I fix this error?

deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    needs: [test] # Correct job name
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun i
      - run: bun run build
      - name: Publish
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          # projectName: ${{ secrets.CLOUDFLARE_PROJECT_NAME }}
          command: pages deploy dist --project-name="$CLOUDFLARE_PROJECT_NAME" --name="$CLOUDFLARE_PROJECT_NAME"
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          secrets: |
            ASTRO_DB_APP_TOKEN
            ASTRO_DB_REMOTE_URL
        env:
          ASTRO_DB_APP_TOKEN: ${{ secrets.ASTRO_DB_APP_TOKEN }}
          ASTRO_DB_REMOTE_URL: ${{ secrets.ASTRO_DB_REMOTE_URL }}

deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    needs: [test] # Correct job name
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun i
      - run: bun run build
      - name: Publish
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          # projectName: ${{ secrets.CLOUDFLARE_PROJECT_NAME }}
          command: pages deploy dist --project-name="$CLOUDFLARE_PROJECT_NAME" --name="$CLOUDFLARE_PROJECT_NAME"
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          secrets: |
            ASTRO_DB_APP_TOKEN
            ASTRO_DB_REMOTE_URL
        env:
          ASTRO_DB_APP_TOKEN: ${{ secrets.ASTRO_DB_APP_TOKEN }}
          ASTRO_DB_REMOTE_URL: ${{ secrets.ASTRO_DB_REMOTE_URL }}

deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    needs: [test] # Correct job name
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun i
      - run: bun run build
      - name: Publish
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          # projectName: ${{ secrets.CLOUDFLARE_PROJECT_NAME }}
          command: pages deploy dist --project-name="$CLOUDFLARE_PROJECT_NAME" --name="$CLOUDFLARE_PROJECT_NAME"
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          secrets: |
            ASTRO_DB_APP_TOKEN
            ASTRO_DB_REMOTE_URL
        env:
          ASTRO_DB_APP_TOKEN: ${{ secrets.ASTRO_DB_APP_TOKEN }}
          ASTRO_DB_REMOTE_URL: ${{ secrets.ASTRO_DB_REMOTE_URL }}

deploy:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      deployments: write
    needs: [test] # Correct job name
    steps:
      - uses: actions/checkout@v4
      - uses: oven-sh/setup-bun@v2
      - run: bun i
      - run: bun run build
      - name: Publish
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          # projectName: ${{ secrets.CLOUDFLARE_PROJECT_NAME }}
          command: pages deploy dist --project-name="$CLOUDFLARE_PROJECT_NAME" --name="$CLOUDFLARE_PROJECT_NAME"
          gitHubToken: ${{ secrets.GITHUB_TOKEN }}
          secrets: |
            ASTRO_DB_APP_TOKEN
            ASTRO_DB_REMOTE_URL
        env:
          ASTRO_DB_APP_TOKEN: ${{ secrets.ASTRO_DB_APP_TOKEN }}
          ASTRO_DB_REMOTE_URL: ${{ secrets.ASTRO_DB_REMOTE_URL }}

Solved: I setup in preCommands with:

wrangler pages secret put ASTRO_DB_APP_TOKEN

wrangler pages secret put ASTRO_DB_APP_TOKEN

wrangler pages secret put ASTRO_DB_APP_TOKEN

wrangler pages secret put ASTRO_DB_APP_TOKEN

J

Jacob•6/5/25, 12:40 AM

Working on cloudflare queues/workers. I noticed that when calling npx wrangler types that it pulls whats in the jsonc plus whats on the server/UI. Issue is sometimes your secrets are out of synch from whats in the UI and your local machine. A git push overrides whatever is there in the UI. The description of this wrangler command says it pulls it in from your bindings but it generates a bunch of old + new types for the ENV bindings of secrets store + standard secrets. Should i play with these config flags? https://developers.cloudflare.com/workers/wrangler/commands/#types

JJames Opstad Have you seen https://blog.cloudflare.com/cloudflare-containers-coming-2025/ ?

A

Avilaa•6/5/25, 12:48 AM

Will it be worth it? Will Cloudflare Containers stand out over platforms?

Y

yinxingmaiming6409•6/5/25, 1:30 PM

I don't understand why a worker can't use all the Node.js modules, so what powerful features can he achieve? Apart from forwarding requests and writing HTML. What else can he do?

S

SnowBall•6/5/25, 1:43 PM

hi

T

top kek•6/5/25, 3:38 PM

how can I share the same D1 db (binding) across two apps in a monorepo?

Yyinxingmaiming6409 I don't understand why a worker can't use all the Node.js modules, so what power...

H

Hard@WorkOP•6/5/25, 4:37 PM

The reason is that Workers runs on

workerd

workerd

, not NodeJS. There is a NodeJS compatibility layer, which adds support for some things, but they are inherently two separate things

I

Isaac McFadyen•6/5/25, 5:02 PM

Apart from forwarding requests and writing HTML

There's lots you can do without Node compat, a lot of people make APIs on Workers, and you can access databases now (plus Hyperdrive if you want to speed them up), or use KV for global read-heavy storage, or R2 for blob storage, etc.

HHard@Work The reason is that Workers runs on `workerd`, not NodeJS. There is a NodeJS comp...

Y

yinxingmaiming6409•6/6/25, 1:03 AM

At present, the advantage of workers seems to be accessing many CloudFlare services without limiting the frequency, right? Higher frequency than HTTP

Ttop kek how can I share the same D1 db (binding) across two apps in a monorepo?

G

Gravite2090•6/6/25, 11:01 PM

One way is to create the same D1 binding in each app's respective wrangler config file. If you are using local based dev and want both your monorepo workers to share the same data, you can use something like this for your run command(s):
wrangler dev --persist-to ../../.wrangler
where ../../.wrangler is the path to the folder where you want the shared data/state to exist

R

relates•6/7/25, 4:09 AM

hello :wave: is the

--yes

--yes

--yes

--yes bugged with

wrangler rollback

wrangler rollback

wrangler rollback

wrangler rollback ?

It doesn't automatically accepts default, I have to manually enter.

D

Dev•6/7/25, 6:52 AM

I'm experiencing these

Authentication error [code: 10000]

Authentication error [code: 10000]

Authentication error [code: 10000]

Authentication error [code: 10000] a lot lately. If it knows how I'm logged in, then why is it giving me errors. I've tried logging out and logging back in

DDev I'm experiencing these `Authentication error [code: 10000]` a lot lately. If it ...

D

Dev•6/7/25, 7:19 AM

it worked now, dont know why it was giving errors

9

9•6/7/25, 9:11 AM

Hello everyone

I'm having an issue with

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote

wrangler dev --remote ( or

npx wrangler dev --remote

npx wrangler dev --remote

npx wrangler dev --remote

npx wrangler dev --remote) in Cloudflare Workers. When I run this command and press 'b' to open the browser, I get redirected from

http://127.0.0.1:8787/

http://127.0.0.1:8787/

http://127.0.0.1:8787/

http://127.0.0.1:8787/ to my production workers.dev URL instead of seeing my development environment.

Terminal shows:

[wrangler:info] GET / 307 Temporary Redirect (14052ms)

[wrangler:info] GET / 307 Temporary Redirect (14052ms)

[wrangler:info] GET / 307 Temporary Redirect (14052ms)

[wrangler:info] GET / 307 Temporary Redirect (14052ms)

I need to use

--remote

--remote

to access my remote D1 database during development, but can't see my dev environment or terminal output.

Wrangler 4.19.1, Node 22.16.0
Config has

preview_urls = true

preview_urls = true

preview_urls = true

preview_urls = true and

workers_dev = true

workers_dev = true

Any ideas how to fix this? Or anything that I can try differently. The problem happens consistently on every retries. Any help is greatly appreciated!

9

9•6/7/25, 9:14 AM

W

Walshy•6/7/25, 9:53 AM

ty

N

nasso•6/7/25, 6:32 PM

guys i think i am going insane, is there any sane way to delete a local d1 database?

sometimes when prototyping you can get your local db all messed up. i often like fully recreating it and applying the migrations (using

wrangler d1 migrations apply

wrangler d1 migrations apply

wrangler d1 migrations apply

wrangler d1 migrations apply)

i added scripts in my

package.json

package.json

like

migrations:apply

migrations:apply

migrations:apply

migrations:apply,

migrations:list

migrations:list

migrations:list

migrations:list,

migrations:gen

migrations:gen

migrations:gen

migrations:gen. how can i make a script that effectively deletes the local db +

migrations:apply

migrations:apply

migrations:apply

migrations:apply??

R

relates•6/8/25, 10:49 AM

do we have command in wrangler for pages rollback? If not, is it planned?

N

nasso•6/9/25, 12:59 PM

okay so you really gotta

rm -rf .wrangler/state

rm -rf .wrangler/state

rm -rf .wrangler/state

rm -rf .wrangler/state
i was hoping there was gonna be a way to get the path to specifically the d1 sqlite file for example but that's good enough for me

N

nasso•6/9/25, 12:59 PM

thank you!

A

ALECKS•6/10/25, 4:15 PM

how do I use wrangler dev to run multiple workers locally at the same time? Say I have:
- auth-svc worker that has a route: ".app.test/auth/"
- api worker with a route: ".app.test/api/"

do I need to handle a proxy in front of each myself, or is there something built into wrangler, or other best practice?

S

Suji•6/10/25, 9:47 PM

Does anyone know how to get the preview url during the build in workers ? (before the version upload)

AALECKS how do I use wrangler dev to run multiple workers locally at the same time? Say ...

S

Silvan•6/10/25, 9:47 PM

well either you just run wrangler dev in both projects or you can also specifcy multiple wrangler files with the -c paramter

Similar Threads

Similar Threads

Similar Threads