Weird question... when making a new Workers project from a github repository, what if I don't _want_

RRobbBoss Weird question... when making a new Workers project from a github repository, wh...

Z

zegevlier•3/14/25, 2:31 PM

You can disable your workers.dev domain before you deploy in your

wrangler.toml/jsonc

wrangler.toml/jsonc

wrangler.toml/jsonc

wrangler.toml/jsonc. https://developers.cloudflare.com/workers/configuration/routing/workers-dev/#disabling-workersdev

C

Chaika•3/14/25, 2:55 PM

Bots should only be from the cert. issuance for *.workername.subdomain.workers.dev anyway, if you deploy and snipe off the workers.dev quick off, should avoid it

C

Chaika•3/14/25, 2:55 PM

for functions?

C

Chaika•3/14/25, 2:55 PM

there's frameworks which can emulate that

C

Chaika•3/14/25, 2:57 PM

yea, eh, I imagine it's one of those things where the vast majority of people use frameworks anyway
I wonder how they're going to try to make that migrate to workers assets

C

Chaika•3/14/25, 2:58 PM

they said in the blog post:

We plan to bridge the gaps between Workers and Pages and provide ways to migrate your Pages projects to Workers.

C

Chaika•3/14/25, 2:59 PM

idk how you'd migrate file path routing without having something to deal with it

C

Chaika•3/14/25, 2:59 PM

maybe just a compat framework or something lol

pages-legacy-routing

pages-legacy-routing

pages-legacy-routing

pages-legacy-routing

CChaika Bots should only be from the cert. issuance for *.workername.subdomain.workers.d...

H

Hello, I’m Allie!•3/14/25, 3:18 PM

You know what would be a real cool and dumb feature for custom domains? Pre-warming. I.e., you activate the domain, issue the cert, but block every request for the first n-minutes

HHello, I’m Allie!You know what would be a real cool and dumb feature for custom domains? Pre-warm...

C

Chaika•3/14/25, 3:20 PM

lol I think you can already do that yourself

C

Chaika•3/14/25, 3:21 PM

I just delete every cert Workers Custom Domains issue before they get a chance to be issued, and either place them on 1st level or use a *.workers.domain.com wildcard acm cert

A

Althaf•3/14/25, 3:24 PM

Hey like i have hosted my vite react app in cloudflare pages and honobackend in the cf workers and there is an issue like when i login the cookie is not present i chrome cookies but in request header it is availabe and also like when i try to logout the cookie is still on the request header and unable to logout on dev no issues. after some reserch i have found like if the front end and backend have different domains like "pages.dev" and "worker.dev" as browser will not save cookie . so is there is a fix for it like without custom domain on dev side the vite proxy works but on production it will not any fix for it

CChaika I just delete every cert Workers Custom Domains issue before they get a chance t...

H

Hello, I’m Allie!•3/14/25, 3:39 PM

I mean the opposite, like in cases where you do want the cert, but don’t want the requests

HHello, I’m Allie!I mean the opposite, like in cases where you do want the cert, but don’t want th...

R

RobbBossOP•3/14/25, 3:42 PM

I like this idea very much. I do think it could help stave off a lot of spurious traffic. I know that it will eventually just result in this pattern being learned, too, but I think its worth exploring

AAlthaf Hey like i have hosted my vite react app in cloudflare pages and honobackend in ...

R

RobbBossOP•3/14/25, 3:47 PM

I might be misunderstanding but this seems like a CORS issue?
I have setup a system that used a custom domain on Pages as the origin and had a Worker in front of it, but they had the same top level domain. I don't think it would have mattered, though, since IIRC even subdomains are normally considered separate domains unless you use CORS.

RRobbBoss I might be misunderstanding but this seems like a CORS issue? I have setup a sy...

A

Althaf•3/14/25, 6:14 PM

i have fixed the cors issue and still this cookie issues persits as on login on application section of chrome doesn't include cookie but on request header will be having it and when logout nothing is happening

A

Althaf•3/14/25, 6:14 PM

and no cors issue is showing on consolelog

N

Nooc•3/15/25, 9:51 AM

Does anybody know the best way to send transactional emails from Cloudflare Workers?

N

Nooc•3/15/25, 9:53 AM

I see MailChannels, but it shows that it stopped sending from Workers last year.

NNooc I see MailChannels, but it shows that it stopped sending from Workers last year.

J

James•3/15/25, 12:51 PM

SendGrid, SES, Postmark, etc. Really anything except MailChannels

NNooc Does anybody know the best way to send transactional emails from Cloudflare Work...

B

Brett Willis•3/16/25, 1:35 AM

I recently jumped from SendGrid to ZeptoMail. Quite a good experience so far, better support experience, and I like their pricing model too.

N

Nooc•3/16/25, 4:22 AM

Thank you very much, I will go take a look at all of these.

M

matt•3/16/25, 8:06 AM

looks like this no longer works with wrangler v4

bunx wrangler secret bulk .dev.vars

bunx wrangler secret bulk .dev.vars

bunx wrangler secret bulk .dev.vars

bunx wrangler secret bulk .dev.vars

M

matt•3/16/25, 8:18 AM

no wait... its

deploy --no-bundle

deploy --no-bundle

deploy --no-bundle

deploy --no-bundle thats failing.it does upload the worker, but after it exits with non-zero exit code. logs show this

Current Version ID: 8699af9c-fdcf-4487-bf6f-fcd0d2076f3a
✘ [ERROR] TypeError: The "options" argument must be of type object. Received an instance of AbortController

      at validateObject (unknown)
      at setTimeoutPromise (node:timers/promises:22:19)
      at <anonymous>
  (/root/.bun/install/global/node_modules/wrangler/wrangler-dist/cli.js:148669:31)
      at processTicksAndRejections (native:7:39)

Current Version ID: 8699af9c-fdcf-4487-bf6f-fcd0d2076f3a
✘ [ERROR] TypeError: The "options" argument must be of type object. Received an instance of AbortController

      at validateObject (unknown)
      at setTimeoutPromise (node:timers/promises:22:19)
      at <anonymous>
  (/root/.bun/install/global/node_modules/wrangler/wrangler-dist/cli.js:148669:31)
      at processTicksAndRejections (native:7:39)

Current Version ID: 8699af9c-fdcf-4487-bf6f-fcd0d2076f3a
✘ [ERROR] TypeError: The "options" argument must be of type object. Received an instance of AbortController

      at validateObject (unknown)
      at setTimeoutPromise (node:timers/promises:22:19)
      at <anonymous>
  (/root/.bun/install/global/node_modules/wrangler/wrangler-dist/cli.js:148669:31)
      at processTicksAndRejections (native:7:39)

Current Version ID: 8699af9c-fdcf-4487-bf6f-fcd0d2076f3a
✘ [ERROR] TypeError: The "options" argument must be of type object. Received an instance of AbortController

      at validateObject (unknown)
      at setTimeoutPromise (node:timers/promises:22:19)
      at <anonymous>
  (/root/.bun/install/global/node_modules/wrangler/wrangler-dist/cli.js:148669:31)
      at processTicksAndRejections (native:7:39)

W

Walshy•3/16/25, 8:25 AM

Can you try with npm?

M

matt•3/16/25, 8:48 AM

i just slapped a

(bunx wrangler ... || true)

(bunx wrangler ... || true)

(bunx wrangler ... || true)

(bunx wrangler ... || true) around it. it throws the same error regardless of command, but it seems to work

E

elpupper•3/16/25, 9:13 AM

anyone else pages nextjs just failing for no reasn?

E

elpupper•3/16/25, 9:14 AM

10:13:23.457    ▲  Error: Command "npm run build" exited with 1

10:13:23.457    ▲  Error: Command "npm run build" exited with 1

10:13:23.457    ▲  Error: Command "npm run build" exited with 1

10:13:23.457    ▲  Error: Command "npm run build" exited with 1

E

elpupper•3/16/25, 9:14 AM

10:13:22.943    ▲  Detected Next.js version: 15.2.2
10:13:22.950    ▲  Running "npm run build"
10:13:23.293    ▲  > falcon-network-site@0.1.0 build
10:13:23.293    ▲  > next build
10:13:23.439    ▲  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
10:13:23.457    ▲  Error: Command "npm run build" exited with 1
10:13:23.645    
10:13:23.645    ⚡️ The Vercel build (`npx vercel build`) command failed. For more details see the Vercel logs above.
10:13:23.646    ⚡️ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.
10:13:23.646    
10:13:23.684    Failed: Error while executing user command. Exited with error code: 1
10:13:23.704    Failed: build command exited with code: 1
10:13:24.922    Failed: error occurred while running build command

10:13:22.943    ▲  Detected Next.js version: 15.2.2
10:13:22.950    ▲  Running "npm run build"
10:13:23.293    ▲  > falcon-network-site@0.1.0 build
10:13:23.293    ▲  > next build
10:13:23.439    ▲  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
10:13:23.457    ▲  Error: Command "npm run build" exited with 1
10:13:23.645    
10:13:23.645    ⚡️ The Vercel build (`npx vercel build`) command failed. For more details see the Vercel logs above.
10:13:23.646    ⚡️ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.
10:13:23.646    
10:13:23.684    Failed: Error while executing user command. Exited with error code: 1
10:13:23.704    Failed: build command exited with code: 1
10:13:24.922    Failed: error occurred while running build command

10:13:22.943    ▲  Detected Next.js version: 15.2.2
10:13:22.950    ▲  Running "npm run build"
10:13:23.293    ▲  > falcon-network-site@0.1.0 build
10:13:23.293    ▲  > next build
10:13:23.439    ▲  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
10:13:23.457    ▲  Error: Command "npm run build" exited with 1
10:13:23.645    
10:13:23.645    ⚡️ The Vercel build (`npx vercel build`) command failed. For more details see the Vercel logs above.
10:13:23.646    ⚡️ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.
10:13:23.646    
10:13:23.684    Failed: Error while executing user command. Exited with error code: 1
10:13:23.704    Failed: build command exited with code: 1
10:13:24.922    Failed: error occurred while running build command

10:13:22.943    ▲  Detected Next.js version: 15.2.2
10:13:22.950    ▲  Running "npm run build"
10:13:23.293    ▲  > falcon-network-site@0.1.0 build
10:13:23.293    ▲  > next build
10:13:23.439    ▲  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
10:13:23.457    ▲  Error: Command "npm run build" exited with 1
10:13:23.645    
10:13:23.645    ⚡️ The Vercel build (`npx vercel build`) command failed. For more details see the Vercel logs above.
10:13:23.646    ⚡️ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.
10:13:23.646    
10:13:23.684    Failed: Error while executing user command. Exited with error code: 1
10:13:23.704    Failed: build command exited with code: 1
10:13:24.922    Failed: error occurred while running build command

W

Walshy•3/16/25, 9:27 AM

▲ You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 >= 20.0.0" is required.

W

Walshy•3/16/25, 9:28 AM

it says the reason

Q

quisi.do•3/16/25, 5:52 PM

Is there not a bug report channel? The timestamps on the Workers Logs page are wrong. 21 minutes ago was not March 5th.

W

Walshy•3/16/25, 6:14 PM

fix is being released monday

M

matt•3/16/25, 11:35 PM

for cloudflare tunnels exposed via public dns, how can i block any connections not from my worker zone? i know i need to write a rule to check

cf.worker.upstream_zone

cf.worker.upstream_zone

cf.worker.upstream_zone

cf.worker.upstream_zone but not sure where

without this rule in place, im seeing a lot of stray requests hitting my http server

Mmatt for cloudflare tunnels exposed via public dns, how can i block any connections n...

H

Hello, I’m Allie!•3/16/25, 11:54 PM

You write it as a WAF Rule: https://developers.cloudflare.com/waf/custom-rules/

Cloudflare Docs

Custom rules · Cloudflare Web Application Firewall (WAF) docs

Custom rules allow you to control incoming traffic by filtering requests to a zone. You can perform actions like Block or Managed Challenge on incoming requests according to rules you define.

M

matt•3/17/25, 12:17 AM

is there another option? i shouldn't have to "talk to a (sales) expert" just to write a single, simple firewall rule

M

matt•3/17/25, 12:20 AM

oh thats just for account-level WAF, not the same as zøne level WAF?

M

matt•3/17/25, 12:30 AM

in the docs, does this rule also allow non-worker requests?

not (cf.worker.upstream_zone in {"" "customer-zone.com"})

not (cf.worker.upstream_zone in {"" "customer-zone.com"})

not (cf.worker.upstream_zone in {"" "customer-zone.com"})

not (cf.worker.upstream_zone in {"" "customer-zone.com"})

if i wanted to allow only requests from workers in my zone, is this one more effective?

not (cf.worker.upstream_zone == "customer-zone.com")

not (cf.worker.upstream_zone == "customer-zone.com")

not (cf.worker.upstream_zone == "customer-zone.com")

not (cf.worker.upstream_zone == "customer-zone.com")

Mmatt in the docs, does this rule also allow non-worker requests? ``` not (cf.worker.u...

C

Cyb3r-Jak3•3/17/25, 12:34 AM

I believe you could do something like

cf.worker.upstream_zone != "customer-zone.com"

cf.worker.upstream_zone != "customer-zone.com"

cf.worker.upstream_zone != "customer-zone.com"

cf.worker.upstream_zone != "customer-zone.com"

M

matt•3/17/25, 12:39 AM

much cleaner, cheers

M

matt•3/17/25, 12:53 AM

just a quick docs bug on https://developers.cloudflare.com/ruleset-engine/rules-language/expressions/#compound-expressions

host

host

host

host ->

http.host

http.host

http.host

http.host

and also not sure if hostname should be string-quoted?

Mmatt just a quick docs bug on https://developers.cloudflare.com/ruleset-engine/rules-...

C

Cyb3r-Jak3•3/17/25, 1:08 AM

Could you file an issue on their GitHub? https://github.com/cloudflare/cloudflare-docs/issues/new?template=content.edit.yml

M

matt•3/17/25, 1:12 AM

done!

G

Greg•3/17/25, 3:19 AM

hey im seeing super weird behavior on a Pages project where seemingly random pages are getting redirected to my static projects 404 page even though the page built without issues, and looks normal when viewing page source from the browser. anybody run into this type of behavior before?

G

Greg•3/17/25, 3:22 AM

here's an example https://60e6c0e8.docs-bao.pages.dev/ensip/1/

I get a 200 response and a normal preview when pinging the page from a tool like HTTPie, but browsers are redirecting to my project's 404 page. I've tested deploying the same project to other platforms and it works as expected, so I believe its somehow related to Cloudflare

S

smalltalk96•3/17/25, 3:50 AM

Hello! How can I use the

--remote

--remote

option with @Cloudflare/vite-plugin to run

npm run dev

npm run dev

npm run dev

npm run dev ?

Ssmalltalk96 Hello! How can I use the `--remote` option with @Cloudflare/vite-plugin to run `...

H

Hello, I’m Allie!•3/17/25, 4:30 AM

I don’t think you can

S

Salisu ahmed•3/17/25, 4:57 AM

Weird question... when making a new Workers project from a github repository, what if I don't _want_

Similar Threads

Similar Threads

Similar Threads