Could you see those variables in the dash?

11984 Ford Laser Could you see those variables in the dash?

I

imightbekyle•11/8/25, 3:03 AM

I could see them yes, but not after ci pipeline deploys

M

mnathl•11/8/25, 3:07 AM

Hey guys if I'm having an issue with a cloudflare error, would I be able to ask for it in this chat? I posted something on the forum, but wasn't sure if I would be able to ask for help here.

Iimightbekyle Cloudflare removing some worker environment variables added in console after dep...

T

texan•11/8/25, 3:34 AM

Recommend checking out https://developers.cloudflare.com/workers/wrangler/configuration/#source-of-truth

Cloudflare Docs

Configuration

Use a configuration file to customize the development and deployment setup for your Worker project and other Developer Platform products.

Mmnathl Hey guys if I'm having an issue with a cloudflare error, would I be able to ask ...

T

texan•11/8/25, 3:35 AM

#workers-and-pages-help thread so it doesn’t get buried (or just ask here!)

Ttexan #workers-and-pages-help thread so it doesn’t get buried (or just ask here!)

M

mnathl•11/8/25, 4:30 AM

Sweet. Yea I asked there before. Basically I'm running into this issue (out of nowhere) where some API requests on my NextJS backend are returning this Cloudflare error:

For context, I'm trying to access my MongoDB collection; however it seems to also happen with other API calls as well. I don't really know where it's come from, it started out of nowhere and the documentation isn't super helpful.

D

Dubz•11/8/25, 8:54 AM

So I have a genuine question. I know that workers are limited to 100k executions per day (on the free plan), and this is shared amongst all account workers, not per-worker. However, there's not really anything preventing users from just making another Cloudflare account to get another 100k executions. Obviously there will be limitations as data can't be shared easily, but if you're making multiple, unrelated projects, that wouldn't matter. Even if a domain is needed on your account, you can get super cheap ones for like $4/yr (which is less than one month of pro plan). Has this ever been considered and thought to change? It'd be cool if we could create "projects" where they have clusters of various services and each of those have their own pool of usage (although I hope that doesn't change them to lower thresholds, in which case forget this entire message lol).

VVJ Hi , I am Vijayabaskar from India, I am building a TANCN (OSS Project), I have m...

V

VJ•11/8/25, 9:46 AM

anyone ? know why is this happening
Here i some additional info , when this happen this is the log that I getting to the user
{"status":500,"unhandled":true,"message":"HTTPError"}

Original message was deleted

D

Dubz•11/8/25, 10:22 AM

If there are legitimate separate purposes though then not entirely. Companies segregate parts of their business under different names for many reasons. That would be separate entities then so not really applicable, and they could realistically spread put whatever they're trying to do with that. Of course there's probably gonna be some person to take things to the extreme with like 50+ accounts just to abuse it and ruin it for everyone else. I only separate mine for business/personal stuff because separation of access is just good practice.

B

Borna Punda•11/8/25, 1:06 PM

Hey, so per-branch/commit previews sound great, but I see one major drawback. Couldn't someone just make a commit that dumps all the environment secrets and use that exfiltrate them? Now, I know only trusted people should have push access, but that is still a privilege escalation.

B

Borna Punda•11/8/25, 1:06 PM

Or do previews not get access to production secrets?

DDubz So I have a genuine question. I know that workers are limited to 100k executions...

P

PhoenixSpace•11/8/25, 1:54 PM

This honestly seems like a massive pain to avoid paying like $5/month

Original message was deleted

B

Borna Punda•11/8/25, 3:16 PM

There are quite a few steps standing between a feature branch and production on well-structured repos

B

Borna Punda•11/8/25, 3:16 PM

Including review processes, CI pipelines, and whatnot

B

Borna Punda•11/8/25, 3:22 PM

But that aside, we figured out how to set non-production builds to a different environment from the dashboard

PPhoenixSpace This honestly seems like a massive pain to avoid paying like $5/month

D

Dubz•11/8/25, 4:29 PM

Honestly you aren't wrong. I only really see kids doing this because they have no money lol

M

mikerowave 🐈•11/9/25, 6:07 AM

just bought a new domain from CF and set it as the domain for a workers project
do i need to do anything else or should i just wait for the domain to work for the project? (ive already rebuilt the project)

M

mikerowave 🐈•11/9/25, 6:14 AM

--
so i got it to work using this guide https://developers.cloudflare.com/workers/configuration/routing/custom-domains/
but when i go to the domain it's not in https

M

mikerowave 🐈•11/9/25, 6:17 AM

ok nvm already fixed it, i thought this was on by default

M

Mazin•11/9/25, 8:05 PM

where can i ask about a problem im having with Browser Rendering ?

MMazin where can i ask about a problem im having with Browser Rendering ?

P

Peps•11/9/25, 8:09 PM

#browser-rendering-api

J

Joy014•11/10/25, 6:02 AM

i have been using "Static Asset hosting" of Cloudflare workers to migrate all my old Cloudflare Pages.
any react, vite, etc project, add below

wrangler.jsonc

wrangler.jsonc

to root of the project, push to Github, add repo to "Create Application" on cloudflare workers page.
There are just 1 config to change, the "static output" folder when

npm run build

npm run build

is run.

{"name":"product-docs","compatibility_date":"2025-09-09","assets":{"directory":"out","not_found_handling":"single-page-application"},"routes":[{"pattern":"xxx.amoga.io","custom_domain":true}]}

{"name":"product-docs","compatibility_date":"2025-09-09","assets":{"directory":"out","not_found_handling":"single-page-application"},"routes":[{"pattern":"xxx.amoga.io","custom_domain":true}]}

{"name":"product-docs","compatibility_date":"2025-09-09","assets":{"directory":"out","not_found_handling":"single-page-application"},"routes":[{"pattern":"xxx.amoga.io","custom_domain":true}]}

{"name":"product-docs","compatibility_date":"2025-09-09","assets":{"directory":"out","not_found_handling":"single-page-application"},"routes":[{"pattern":"xxx.amoga.io","custom_domain":true}]}

Sstavros-k Hi! I'm trying to increase the project (pages) limits (100). Tried both the form...

S

stavros-k•11/10/25, 10:09 AM

Can someone please reply?

Sstavros-k ☁️☁️☁️ ‼️ Can someone please reply?

1

1984 Ford LaserOP•11/10/25, 7:50 PM

If you were using Workers instead of Pages the limit is 500

S

stavros-k•11/10/25, 7:51 PM

But it’s static sites. How would that work?

J

jordanthornquest•11/10/25, 7:57 PM

If I have, say, a React application running on Cloudflare Workers and I want to make an API request to the Cloudflare API, and I need to pass my

CLOUDFLARE_ACCOUNT_ID

CLOUDFLARE_ACCOUNT_ID

and

CLOUDFLARE_API_TOKEN

CLOUDFLARE_API_TOKEN

to the API request, are either of those environment variables automatically defined in the Workers runtime, or do I need to explicitly add those to my project's configuration?

Sstavros-k But it’s static sites. How would that work?

H

Hard@Work•11/10/25, 7:58 PM

https://developers.cloudflare.com/workers/static-assets/

Cloudflare Docs

Static Assets

Create full-stack applications deployed to Cloudflare Workers.

S

stavros-k•11/10/25, 8:14 PM

I’ll check it out. Is there any differences that I should be aware when migrating?

Sstavros-k I’ll check it out. Is there any differences that I should be aware when migratin...

1

1984 Ford LaserOP•11/10/25, 9:47 PM

I haven't tried it, but this might help: https://developers.cloudflare.com/workers/static-assets/migration-guides/migrate-from-pages/

J

jordanthornquest•11/10/25, 10:21 PM

Is the IP list on
https://www.cloudflare.com/ips/
https://www.cloudflare.com/ips/
up-to-date? My deployed Worker is making an REST API request from an IP that isn't on this list. Ignore that, I'm a bonehead and didn't know how IP ranges worked hahaha

S

stavros-k•11/10/25, 11:14 PM

Does wrangler deploy or wranger versions upload support JSON output? (ie I want to extract URL of the preview)

S

stavros-k•11/10/25, 11:19 PM

I suppose each "worker" is equivalent to a "project"?

W

Walshy•11/10/25, 11:51 PM

see https://github.com/cloudflare/cloudflare-docs/pull/26259

W

Walshy•11/10/25, 11:52 PM

or you can grep it out easily too

W

Walshy•11/10/25, 11:52 PM

and yes

W

Walshy•11/10/25, 11:52 PM

Though reading the past responses, if you hit the 100 pages project limit - you may want Workers for Platforms to have unlimited Workers. Depends on what you're doing but it sounds platform-y

G

Gonzalo•11/11/25, 1:31 AM

Hi. I am getting this error when trying to create a worker. What could be the issue?

GGonzalo Hi. I am getting this error when trying to create a worker. What could be the is...

1

1984 Ford LaserOP•11/11/25, 2:22 AM

Does it do this with any project name? If you open the console window, I wonder what the error message actually is

WWalshy Though reading the past responses, if you hit the 100 pages project limit - you ...

S

stavros-k•11/11/25, 6:27 AM

Workers have 500 on paid plan right? The “number of workers” is equivalent to “projects”?

W

Walshy•11/11/25, 6:28 AM

yes

W

Walshy•11/11/25, 6:28 AM

but why do you need 500

W

Walshy•11/11/25, 6:28 AM

If you're doing a platform kind of thing, you should use workers for platforms so you can also scale above 500

S

stavros-k•11/11/25, 6:28 AM

We need a few more above the 100. Some new stores arised

S

stavros-k•11/11/25, 6:29 AM

Not platform things! Just landing/marketing pages for franchises

S

stavros-k•11/11/25, 6:34 AM

Alright. This seems viable! And tbh it feels better to having to pay something lol. It was feeling like cheating to having all these on free tier so far!

A

ak5•11/11/25, 6:35 AM

hi trying to find out what node versions are supported by worker, I am trying to put 22.21.0 but i am getting something like

14:19:57.342    Initializing build environment...
14:19:59.970    Success: Finished initializing build environment
14:20:00.993    Cloning repository...
14:20:02.796    Restoring from dependencies cache
14:20:02.799    Restoring from build output cache
14:20:04.515    Detected the following tools from environment: pnpm@10.19.0, nodejs@22.16.0
14:20:06.553    Installing project dependencies: pnpm install --frozen-lockfile
14:20:07.157     ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)
14:20:07.157    
14:20:07.157    Your Node version is incompatible with "/opt/buildhome/repo".
14:20:07.157    
14:20:07.157    Expected version: 22.21.0
14:20:07.158    Got: v22.16.0
14:20:07.158    
14:20:07.158    This is happening because the package's manifest has an engines.node field specified.
14:20:07.158    To fix this issue, install the required Node version.
14:20:07.197    Failed: error occurred while installing tools or dependencies

14:19:57.342    Initializing build environment...
14:19:59.970    Success: Finished initializing build environment
14:20:00.993    Cloning repository...
14:20:02.796    Restoring from dependencies cache
14:20:02.799    Restoring from build output cache
14:20:04.515    Detected the following tools from environment: pnpm@10.19.0, nodejs@22.16.0
14:20:06.553    Installing project dependencies: pnpm install --frozen-lockfile
14:20:07.157     ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)
14:20:07.157    
14:20:07.157    Your Node version is incompatible with "/opt/buildhome/repo".
14:20:07.157    
14:20:07.157    Expected version: 22.21.0
14:20:07.158    Got: v22.16.0
14:20:07.158    
14:20:07.158    This is happening because the package's manifest has an engines.node field specified.
14:20:07.158    To fix this issue, install the required Node version.
14:20:07.197    Failed: error occurred while installing tools or dependencies

14:19:57.342    Initializing build environment...
14:19:59.970    Success: Finished initializing build environment
14:20:00.993    Cloning repository...
14:20:02.796    Restoring from dependencies cache
14:20:02.799    Restoring from build output cache
14:20:04.515    Detected the following tools from environment: pnpm@10.19.0, nodejs@22.16.0
14:20:06.553    Installing project dependencies: pnpm install --frozen-lockfile
14:20:07.157     ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)
14:20:07.157    
14:20:07.157    Your Node version is incompatible with "/opt/buildhome/repo".
14:20:07.157    
14:20:07.157    Expected version: 22.21.0
14:20:07.158    Got: v22.16.0
14:20:07.158    
14:20:07.158    This is happening because the package's manifest has an engines.node field specified.
14:20:07.158    To fix this issue, install the required Node version.
14:20:07.197    Failed: error occurred while installing tools or dependencies

14:19:57.342    Initializing build environment...
14:19:59.970    Success: Finished initializing build environment
14:20:00.993    Cloning repository...
14:20:02.796    Restoring from dependencies cache
14:20:02.799    Restoring from build output cache
14:20:04.515    Detected the following tools from environment: pnpm@10.19.0, nodejs@22.16.0
14:20:06.553    Installing project dependencies: pnpm install --frozen-lockfile
14:20:07.157     ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)
14:20:07.157    
14:20:07.157    Your Node version is incompatible with "/opt/buildhome/repo".
14:20:07.157    
14:20:07.157    Expected version: 22.21.0
14:20:07.158    Got: v22.16.0
14:20:07.158    
14:20:07.158    This is happening because the package's manifest has an engines.node field specified.
14:20:07.158    To fix this issue, install the required Node version.
14:20:07.197    Failed: error occurred while installing tools or dependencies

I used engines and packageManager keys in package.json

S

stavros-k•11/11/25, 6:35 AM

Next step figure out a better way to manage assets.
A big portion of those sites use almost the same assets, having to bundle them on each one and do optimisation on build takes a lot of time if you do it x100.

A

armorstudiosdevops•11/11/25, 6:45 AM

Is anyone having issues with workers not rendering their app correctly? I have double checked my wrangler.jsonc and worker/index.ts no errors.

A

armorstudiosdevops•11/11/25, 6:48 AM

It renders fine on vibe-sdk but once deployed to workers it doesn't look like it did in the preview

A

armorstudiosdevops•11/11/25, 6:48 AM

I used bun run build and bun run deploy from terminal

A

ak5•11/11/25, 7:29 AM

i had to add a .node-version with

v22.21.0

v22.21.0

v22.21.0

v22.21.0 and then it worked, looks like it doesn't respect engines.node in package.json

Could you see those variables in the dash?

Similar Threads

Similar Threads

Similar Threads