i was facing an issue deploying a worker to dispatch namespace. with durable object bindings and mig

SStadl0r Hey! Has anyone experienced CORS policy issue as of `wrangler 3.62` when using `...

S

sukuna•7/11/24, 1:29 PM

Should be fine

MMayuresh Choudhary downgrade your Wrangler version to 3.61.0 or less and use wrangler dev (or wrang...

A

Arpit•7/11/24, 5:10 PM

faced the same problem in 3.61.0 as well

M

mahineeli•7/13/24, 1:56 PM

hello, I have created new cloudflare app. after installing when i ran the command

npm run dev

npm run dev

npm run dev

npm run dev /

npm start

npm start

npm start

npm start te following error is thrown, can anyone help me why is this happening.
error:

 node_modules\wrangler\wrangler-dist\cli.js:29765
            throw a;
            ^

Error: write EOF
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
    at WriteWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
  errno: -4095,
  code: 'EOF',
  syscall: 'write'
}

Node.js v18.18.2

 node_modules\wrangler\wrangler-dist\cli.js:29765
            throw a;
            ^

Error: write EOF
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
    at WriteWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
  errno: -4095,
  code: 'EOF',
  syscall: 'write'
}

Node.js v18.18.2

 node_modules\wrangler\wrangler-dist\cli.js:29765
            throw a;
            ^

Error: write EOF
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
    at WriteWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
  errno: -4095,
  code: 'EOF',
  syscall: 'write'
}

Node.js v18.18.2

 node_modules\wrangler\wrangler-dist\cli.js:29765
            throw a;
            ^

Error: write EOF
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
    at WriteWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
  errno: -4095,
  code: 'EOF',
  syscall: 'write'
}

Node.js v18.18.2

Mmahineeli hello, I have created new cloudflare app. after installing when i ran the comman...

M

mahineeli•7/13/24, 6:20 PM

npm run deploy

npm run deploy

npm run deploy

npm run deploy deployed the application successfully, still local dev is not working.Why?

J

Jakob Norlin•7/18/24, 12:03 PM

Does

getPlatformProxy

getPlatformProxy

getPlatformProxy

getPlatformProxy not support RPCs?

I'm trying to access RPCs from a worker in a pages project, and I'm using

getPlatformProxy

getPlatformProxy

getPlatformProxy

getPlatformProxy to access the cloudflare env in local development.

However, when trying to call an RPC on a bound service, I get the following error:

DevalueError: Cannot stringify POJOs with symbolic keys
    at flatten (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:145:13)
    ... 3 lines matching cause stack trace ...
    at async ProxyServer.fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:157:11) {
  cause: Error [DevalueError]: Cannot stringify POJOs with symbolic keys
      at flatten (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:145:13)
      at stringify (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:178:16)
      at stringifyWithStreams (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/devalue.ts:242:27)
      at #fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:342:30)
      at async ProxyServer.fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:157:11)

DevalueError: Cannot stringify POJOs with symbolic keys
    at flatten (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:145:13)
    ... 3 lines matching cause stack trace ...
    at async ProxyServer.fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:157:11) {
  cause: Error [DevalueError]: Cannot stringify POJOs with symbolic keys
      at flatten (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:145:13)
      at stringify (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:178:16)
      at stringifyWithStreams (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/devalue.ts:242:27)
      at #fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:342:30)
      at async ProxyServer.fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:157:11)

DevalueError: Cannot stringify POJOs with symbolic keys
    at flatten (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:145:13)
    ... 3 lines matching cause stack trace ...
    at async ProxyServer.fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:157:11) {
  cause: Error [DevalueError]: Cannot stringify POJOs with symbolic keys
      at flatten (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:145:13)
      at stringify (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:178:16)
      at stringifyWithStreams (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/devalue.ts:242:27)
      at #fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:342:30)
      at async ProxyServer.fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:157:11)

DevalueError: Cannot stringify POJOs with symbolic keys
    at flatten (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:145:13)
    ... 3 lines matching cause stack trace ...
    at async ProxyServer.fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:157:11) {
  cause: Error [DevalueError]: Cannot stringify POJOs with symbolic keys
      at flatten (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:145:13)
      at stringify (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/.pnpm/devalue@4.3.2/node_modules/devalue/src/stringify.js:178:16)
      at stringifyWithStreams (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/devalue.ts:242:27)
      at #fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:342:30)
      at async ProxyServer.fetch (~/project/node_modules/.pnpm/miniflare@3.20240701.0/node_modules/miniflare/src/workers/core/proxy.worker.ts:157:11)

If I call the RPC from a regular workers project it works just fine.

Wrangler version 3.65.0

J

Jakob Norlin•7/18/24, 12:08 PM

The above error is from this code snippet

const { getPlatformProxy } = await import("wrangler")
const platform = await getPlatformProxy()
console.log(await platform.env.MY_SERVICE.testRPCFunction())

const { getPlatformProxy } = await import("wrangler")
const platform = await getPlatformProxy()
console.log(await platform.env.MY_SERVICE.testRPCFunction())

const { getPlatformProxy } = await import("wrangler")
const platform = await getPlatformProxy()
console.log(await platform.env.MY_SERVICE.testRPCFunction())

const { getPlatformProxy } = await import("wrangler")
const platform = await getPlatformProxy()
console.log(await platform.env.MY_SERVICE.testRPCFunction())

D

Dario•7/18/24, 1:51 PM

getPlatformProxy

getPlatformProxy

getPlatformProxy

getPlatformProxy should definitely support RPC: https://github.com/cloudflare/workers-sdk/blob/e7c06d78b14eb89060f431bc4aee8dbc1cc08fa5/fixtures/get-platform-proxy/tests/get-platform-proxy.env.test.ts#L182

I think this is blowing up in the Miniflare magic proxy as the code is trying to send some non serializable object across the wire (the error message comes from devalue which the magic proxy uses to serialize values: https://github.com/Rich-Harris/devalue/blob/0c35c0e7a6a37172c7f049eaae4e7079559ba250/src/stringify.js#L149)

@Jakob Norlin would you be able to spin up a minimal reproduction of the issue?

(if you want please feel free to create a workers-sdk issue and tag me there: https://github.com/cloudflare/workers-sdk/issues/new/choose)

GitHub

devalue/src/stringify.js at 0c35c0e7a6a37172c7f049eaae4e7079559ba25...

Gets the job done when JSON.stringify can't. Contribute to Rich-Harris/devalue development by creating an account on GitHub.

GitHub

workers-sdk/fixtures/get-platform-proxy/tests/get-platform-proxy.en...

Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk

DDario `getPlatformProxy` should definitely support RPC: https://github.com/cloudflare/...

J

Jakob Norlin•7/18/24, 6:29 PM

Here's the minimal repro: https://github.com/jakst/wrangler-rpc-platform-proxy. I'll create an issue in a sec

J

Jakob Norlin•7/18/24, 6:36 PM

And here's the issue https://github.com/cloudflare/workers-sdk/issues/6285

GitHub

🐛 BUG: Error `Cannot stringify POJOs with symbolic keys` when calli...

Which Cloudflare product(s) does this pertain to? Wrangler, Miniflare What version(s) of the tool(s) are you using? 3.65.o [wrangler] What version of Node are you using? 22.4.1 What operating syste...

D

Dario•7/18/24, 8:29 PM

oh.... wow this is very very basic... I was hoping that you might have been doing something specific on your side that was causing the issue... bizarre.... I now wonder if the workers-sdk tests are actually running!

D

Dario•7/18/24, 8:29 PM

anyways thanks so much this is great!

D

Dario•7/18/24, 8:30 PM

I will look into this as soon as I can

(probably this saturday)

J

Jakob Norlin•7/19/24, 1:04 PM

Good to hear! Looking forward to the results

M

Martin•7/19/24, 4:47 PM

hi i'm trying to automate the syncing of my secrets so biasing towards using wrangler for managing them.. the CLI is showing secrets but I don't see them in the dashboard and my app also isn't getting them in context.

✗ wrangler secret list -c wrangler.toml
[
  {
    "name": "CF_ACCESS_KEY_ID",
    "type": "secret_text"
  },

✗ wrangler secret list -c wrangler.toml
[
  {
    "name": "CF_ACCESS_KEY_ID",
    "type": "secret_text"
  },

✗ wrangler secret list -c wrangler.toml
[
  {
    "name": "CF_ACCESS_KEY_ID",
    "type": "secret_text"
  },

✗ wrangler secret list -c wrangler.toml
[
  {
    "name": "CF_ACCESS_KEY_ID",
    "type": "secret_text"
  },

one thing I noticed is that

-e foo

-e foo

-e foo

-e foo seemingly makes no difference, list returns results irrespective of the environment i specify. Am I missing something obvious?

M

Martin•7/19/24, 4:59 PM

ah bloop. should be writing via

wrangler pages secret

wrangler pages secret

wrangler pages secret

wrangler pages secret .. workers/pages bites me again

Ɽ

ⱤØ₥₳₦•7/20/24, 3:25 AM

what it means? code is correct and npx wrangler dev command was working fine yesterday, now it is throwing this error

W

Walshy•7/21/24, 4:28 PM

yes, wrangler.toml is safe to commit

I

isaiah•7/22/24, 12:09 AM

Is there a way to use

create-cloudflare

create-cloudflare

create-cloudflare

create-cloudflare without installing

wrangler

wrangler

wrangler

wrangler again? I have wrangler installed globally already and I'm the only one working with my code.

J

James•7/22/24, 12:11 AM

create-cloudflare

create-cloudflare

create-cloudflare

create-cloudflare is a separate package. If you run

npx create cloudflare@latest

npx create cloudflare@latest

npx create cloudflare@latest

npx create cloudflare@latest and already have the latest version, it won't try and re-download it

J

jLynx•7/22/24, 2:45 AM

Hey everyone, I am trying to setup jest unit testing for my functions. I have my example dir set up like this:
functions/
functions/user.ts
functions/user.test.ts

This works fine in the fact that I can run the jest tests and I can also run wrangler. But Wrangler constantly complains (See screenshot). Why are these even popping up when I am trying to run my page/functions. How do I exclude them so they do not show up while I am running locally?

B

broooo•7/23/24, 6:34 AM

how to fix this issue?

F

Flare•7/23/24, 9:16 AM

Please do not post your question in multiple channels per the rules at #

welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

Original message was deleted

B

broooo•7/23/24, 10:52 AM

huh?

Bbroooo huh?

H

Hard@Work•7/23/24, 10:53 AM

You have posted the above issue in multiple different channels. This can cause confusion, as multiple people may answer your question, and not notice each other

H

Hard@Work•7/23/24, 10:56 AM

In addition, if you provide context in one channel, others may not notice, and it may take them longer to be able to provide you an answer

B

broooo•7/23/24, 11:18 AM

i did cause no one was answering,

R

Roshan_Neupane•7/23/24, 12:03 PM

CF_ACCOUNT_ID env var doesnt overwrite the cached value in wrangler-account.json. I wanted to deploy to cloudflare pages, and everytime i do that the account id might be different. So, any suggestions?

I

iwgu•7/24/24, 7:06 PM

Is there a way to get the environment information on which worker is being deployed on in custom builds?
What I mean is, I have a script which runs before deployement and does some stuff, but it needs to know the environment
Which I pass to wrangler as
wrangler deploy --env prod
wrangler deploy --env prod
wrangler deploy --env prod
wrangler deploy --env prod I looked to env variables but I dont think wrangler relays this to custom build script

NVM build is not top-level only directive so i just placed it under [env.prod]

K

Kuanglu•7/25/24, 3:18 AM

What should I do if I want to use

wrangler dev

wrangler dev

locally to test fetch origin address ?
~~~

KKuanglu What should I do if I want to use `wrangler dev` locally to test fetch origin ad...

K

Kuanglu•7/25/24, 3:20 AM

export default {
async fetch(request, env, ctx) {
// fetch origin server
const res = await fetch(request.url);
return new Response(res);
},
};

Iiwgu ~~Is there a way to get the environment information on which worker is being dep...

R

Roshan_Neupane•7/25/24, 11:13 AM

is that the answer to my question? If it is, then should i change the env.prod everytime? and does it overwrite the cache?

RRoshan_Neupane is that the answer to my question? If it is, then should i change the env.prod e...

I

iwgu•7/25/24, 12:43 PM

No I was asking a question then found my answer, unfortunately i have no idea what wrangler-account.json is

C

Cole•7/25/24, 2:47 PM

Has anyone seen an issue where

wrangler pages dev

wrangler pages dev

wrangler pages dev

wrangler pages dev doesn't start the server unless you restart your computer (macOS arm, bun)?
It also hangs when you try to shut down the server

#:schema node_modules/wrangler/config-schema.json
name = "phosphor-server"
compatibility_date = "2024-07-12"
compatibility_flags = ["nodejs_compat"]
no_bundle = true

#:schema node_modules/wrangler/config-schema.json
name = "phosphor-server"
compatibility_date = "2024-07-12"
compatibility_flags = ["nodejs_compat"]
no_bundle = true

#:schema node_modules/wrangler/config-schema.json
name = "phosphor-server"
compatibility_date = "2024-07-12"
compatibility_flags = ["nodejs_compat"]
no_bundle = true

#:schema node_modules/wrangler/config-schema.json
name = "phosphor-server"
compatibility_date = "2024-07-12"
compatibility_flags = ["nodejs_compat"]
no_bundle = true

2024-07-25_.dev.vars_phosphor_Workspace_at_11.47AM2x.png

C

Cole•7/25/24, 2:57 PM

Anyone seen this before? No such module "wrangler:modules-watch"

⎔ Starting local server...
[wrangler:inf] Ready on http://localhost:5010
✘ [ERROR] service core:user:phosphor-server: Uncaught Error: No such module "wrangler:modules-watch".

    imported from "_worker.js"


✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

⎔ Starting local server...
[wrangler:inf] Ready on http://localhost:5010
✘ [ERROR] service core:user:phosphor-server: Uncaught Error: No such module "wrangler:modules-watch".

    imported from "_worker.js"


✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

⎔ Starting local server...
[wrangler:inf] Ready on http://localhost:5010
✘ [ERROR] service core:user:phosphor-server: Uncaught Error: No such module "wrangler:modules-watch".

    imported from "_worker.js"


✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

⎔ Starting local server...
[wrangler:inf] Ready on http://localhost:5010
✘ [ERROR] service core:user:phosphor-server: Uncaught Error: No such module "wrangler:modules-watch".

    imported from "_worker.js"


✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

2024-07-25_vite.config.ts_phosphor_Workspace_at_11.56AM2x.png

0

0x44617461486561727468•7/25/24, 3:17 PM

Hello there! I have some issues with local development using

wrangler pages dev

wrangler pages dev

wrangler pages dev

wrangler pages dev and

vite build

vite build

vite build

vite build for a

sveltekit

sveltekit

sveltekit

sveltekit app with the local

D1

D1

D1

D1 database. I can access my landing page, but most of generated scripts by

vite

vite

vite

vite are not served by

wrangler

wrangler

wrangler

wrangler. Example:

[wrangler:inf] GET /_app/immutable/entry/start.C9uj9_pe.js 404 Not Found (13ms)

[wrangler:inf] GET /_app/immutable/entry/start.C9uj9_pe.js 404 Not Found (13ms)

[wrangler:inf] GET /_app/immutable/entry/start.C9uj9_pe.js 404 Not Found (13ms)

[wrangler:inf] GET /_app/immutable/entry/start.C9uj9_pe.js 404 Not Found (13ms)

0

0x44617461486561727468•7/25/24, 3:17 PM

Another issue (might be related) is with the

--live-reload

--live-reload

--live-reload

--live-reload flag. Is doesn't reload nor update the page with whatever modifications I've done.

0

0x44617461486561727468•7/25/24, 3:18 PM

Any idea where to dig? I can provide the

wrangler.toml

wrangler.toml

wrangler.toml

wrangler.toml,

svelte.config.js

svelte.config.js

svelte.config.js

svelte.config.js and scripts ran during launch

Y

yaniv.efraim•7/29/24, 3:31 PM

Hello...
I want to create a custom domain with a wildcard, something like

routes = [
    { pattern = "*.mydomain.com/*", custom_domain = true }
]

routes = [
    { pattern = "*.mydomain.com/*", custom_domain = true }
]

routes = [
    { pattern = "*.mydomain.com/*", custom_domain = true }
]

routes = [
    { pattern = "*.mydomain.com/*", custom_domain = true }
]

Which fails with:

✘ [ERROR] Cannot use "*.wix-app-test2.run/*" as a Custom Domain; wildcard operators (*) are not allowed

✘ [ERROR] Cannot use "*.wix-app-test2.run/*" as a Custom Domain; wildcard operators (*) are not allowed

✘ [ERROR] Cannot use "*.wix-app-test2.run/*" as a Custom Domain; wildcard operators (*) are not allowed

✘ [ERROR] Cannot use "*.wix-app-test2.run/*" as a Custom Domain; wildcard operators (*) are not allowed

Now, I know that this is possible from withing the Dashboard (we have such a custom domain). This means that we cannot use our Wrangler integration, because it will eigther fail, or remove the wildcard setup (if I don't have it in my wrangler config).
Is there a solution for that?

Yyaniv.efraim Hello... I want to create a custom domain with a wildcard, something like ``` r...

H

Hard@Work•7/29/24, 3:37 PM

Try

routes = [
    { pattern = "*.wix-app-test2.run/*", zone_name = "wix-app-test2.run" }
]

routes = [
    { pattern = "*.wix-app-test2.run/*", zone_name = "wix-app-test2.run" }
]

routes = [
    { pattern = "*.wix-app-test2.run/*", zone_name = "wix-app-test2.run" }
]

routes = [
    { pattern = "*.wix-app-test2.run/*", zone_name = "wix-app-test2.run" }
]

S

sia•7/29/24, 5:06 PM

Dumb question, should i add the .wrangler directory to my .gitignore file? I can't find it mentioned in the docs anywhere

Ssia Dumb question, should i add the .wrangler directory to my .gitignore file? I can...

H

Hard@Work•7/29/24, 5:20 PM

Yes, it stores temporary files and local storage for the cache, R2, D1, etc.

HHard@Work Try ```toml routes = [ { pattern = "*.wix-app-test2.run/*", zone_name = "wix...

Y

yaniv.efraim•7/30/24, 7:20 AM

Thanks!
I tried that, but then it creates the route under

Routes

Routes

Routes

Routes, but not under

Custom Domains

Custom Domains

Custom Domains

Custom Domains. This is confusing...

Yyaniv.efraim Thanks! I tried that, but then it creates the route under `Routes`, but not und...

H

Hard@Work•7/30/24, 7:54 AM

Is there any reason why you need a "custom domain" specifically? In this case, Custom Domains only support

wix-app-test2.run

wix-app-test2.run

wix-app-test2.run

wix-app-test2.run directly

H

Hard@Work•7/30/24, 7:55 AM

Oh, if it wasn't clear, Routes and Custom Domains are mostly the same thing. A Custom Domain is basically just a route covering

wix-app-test2.run/*

wix-app-test2.run/*

wix-app-test2.run/*

wix-app-test2.run/*, with automatic DNS record creation and Certificate Issuance

HHard@Work Oh, if it wasn't clear, Routes and Custom Domains are *mostly* the same thing. A...

Y

yaniv.efraim•7/30/24, 7:56 AM

hmmm, this is confusing...
So, if I need a wildcard to work, something like

*.wix-app-test2.run/*

*.wix-app-test2.run/*

*.wix-app-test2.run/*

*.wix-app-test2.run/*

What should I use?
Thanks!

H

Hard@Work•7/30/24, 7:56 AM

For single-level subdomains, Universal SSL should already cover the route you want anyway, so the only thing you would need to do is create a dummy DNS record for

*.wix-app-test2.run

*.wix-app-test2.run

*.wix-app-test2.run

*.wix-app-test2.run(pointing to AAAA

100::

100::

100::

100::

Yyaniv.efraim hmmm, this is confusing... So, if I need a wildcard to work, something like ``...

H

Hard@Work•7/30/24, 7:57 AM

I would do the route as above, then create the AAAA Record

HHard@Work I would do the route as above, then create the AAAA Record

Y

yaniv.efraim•7/30/24, 8:29 AM

Not sure that I understand the dummy DNS record (sorry, new here....)
This one I understand:

routes = [
    { pattern = "*.wix-app.run/*", zone_name = "wix-app.run" }
]

routes = [
    { pattern = "*.wix-app.run/*", zone_name = "wix-app.run" }
]

routes = [
    { pattern = "*.wix-app.run/*", zone_name = "wix-app.run" }
]

routes = [
    { pattern = "*.wix-app.run/*", zone_name = "wix-app.run" }
]

Then manually create a DNS record (from the Dashbord)? Like this:

i was facing an issue deploying a worker to dispatch namespace. with durable object bindings and mig

Similar Threads

Similar Threads

Similar Threads