Though reading the past responses, if you hit the 100 pages project limit - you may want Workers for

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 Laser•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

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

yes

W

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

but why do you need 500

W

WalshyOP•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

H

hypecity_host•11/11/25, 7:39 AM

Hello

H

hypecity_host•11/11/25, 7:40 AM

Im trying to change the origin IP for a request using cloudflare snippets. But im Receiving "direct IP Access Not allowed" Error. Pointing it to a random Domain however works. Is there a workaround to this?

H

hypecity_host•11/11/25, 7:42 AM

Basically what im doing is newUrl.hostname = (the new IP of the Backend Server)

Original message was deleted

H

hypecity_host•11/11/25, 8:44 AM

So If i were to make a Domain that Points to all IPS (for example 10-10-10-10.ip-address.com) it will Work?

Original message was deleted

H

hypecity_host•11/11/25, 9:06 AM

Well im afraid thats the only way i can do what i wanted to do

S

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

When using CF image resizing (via

/cdn-cgi/image/.../my-image-path

/cdn-cgi/image/.../my-image-path

/cdn-cgi/image/.../my-image-path

/cdn-cgi/image/.../my-image-path) where the image path is in a static asset of the worker, do I only get "charged" with

Images Transformed

Images Transformed

Images Transformed

Images Transformed or does it also "charges"

Images Delivered

Images Delivered

Images Delivered

Images Delivered?

S

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

I suppose only images transformed

Sstavros-k When using CF image resizing (via `/cdn-cgi/image/.../my-image-path`) where the ...

1

1984 Ford Laser•11/11/25, 10:06 AM

Pretty sure it's just transforms but I would need to track my usage more closely to be sure. Lemme check in the morning when I'm back at my PC

S

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

Thanks.
Also, website.domain1.com/my-image.png and website.domain2.com/my-image.png (where both images are the same actual file).
Do I get double "charged" for the transformation because its a different zone?

S

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

Hmm, I have 80% identical images across multiple websites. This doesn't sound good

S

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

Hmm even subdomains of the same domain count as different transformations

Sstavros-k Hmm even subdomains of the same domain count as different transformations

1

1984 Ford Laser•11/11/25, 10:26 AM

Every unique url is a unique transformation

S

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

ie www.domain.com/ and domain.com/ will count as different transforms

1

1984 Ford Laser•11/11/25, 10:27 AM

You should use a white label approach to these images, use something like domain1.company-name.com/images/url-whatever

S

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

Like have a worker that has only the assets? And then websites will just use the URL of that worker for the images

1

1984 Ford Laser•11/11/25, 10:29 AM

Basically just use the same image url for these different sites

S

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

I remember CF had something in ToS at some point that prevented having too many images compared to html.

1

1984 Ford Laser•11/11/25, 10:29 AM

Use your company name for the images URL, you could use a worker to rewrite URLs before they're presented to the client or something

Sstavros-k I remember CF had something in ToS at some point that prevented having too many ...

1

1984 Ford Laser•11/11/25, 10:29 AM

Are you sure?

1

1984 Ford Laser•11/11/25, 10:30 AM

How many images are we talking lmao you should be able to deliver millions with Images

S

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

I found this from reddit, but it seems its for tunnels.

Use of the Services for serving video or a disproportionate percentage of pictures, audio files, or other non-HTML content is prohibited"

Use of the Services for serving video or a disproportionate percentage of pictures, audio files, or other non-HTML content is prohibited"

Use of the Services for serving video or a disproportionate percentage of pictures, audio files, or other non-HTML content is prohibited"

Use of the Services for serving video or a disproportionate percentage of pictures, audio files, or other non-HTML content is prohibited"

11984 Ford Laser How many images are we talking lmao you should be able to deliver millions with ...

S

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

Its <600 per website (well not in a single page)
But are the same ones across all websites

1

1984 Ford Laser•11/11/25, 10:35 AM

Oh that'll be no worriee I generate hundreds of not thousands of transformations a month. Use Workers to generate small images from strings in rust then overlay them with Transformations, some pipelines can generate 300+ images

1

1984 Ford Laser•11/11/25, 10:36 AM

Why not just store them on R2?

1

1984 Ford Laser•11/11/25, 10:36 AM

600 images would be within the included usage probably

S

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

Then I need custom ~~tooling~~ ci steps to also upload them there.
I was thinking just a worker for assets with custom domain

images.my-domain.com

images.my-domain.com

images.my-domain.com

images.my-domain.com
Then on all other websites I just use

images.my-domain.com/cdn-cgi/image/.../img-path

images.my-domain.com/cdn-cgi/image/.../img-path

images.my-domain.com/cdn-cgi/image/.../img-path

images.my-domain.com/cdn-cgi/image/.../img-path. Single transformation and single source of truth.

Sstavros-k Then I need custom ~~tooling~~ ci steps to also upload them there. I was thinkin...

1

1984 Ford Laser•11/11/25, 10:40 AM

Yeah that makes sense! I like it

S

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

Perfect. Once I migrate pages to workers, thats the next project.

Currently I spent awful lots of time to do image optimization during build time and do the same thing for each website.
(next js + next image export)

Should shave tons of time

S

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

Oh that would allow to build a small page to browse the images by category as well on the same worker

Sstavros-k Perfect. Once I migrate pages to workers, thats the next project. Currently I s...

1

1984 Ford Laser•11/11/25, 10:46 AM

Are your NextJS sites all basically the same as each other, minus some minor changes for diff clients? I wonder if there's a way to use SSR to have 1 Worker which serves all of these different sites depending on the domain or something

1

1984 Ford Laser•11/11/25, 10:47 AM

Just random idea

S

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

Thats the very very long term game. Because when started we had some clients that wanted to use their own infra (apache on vps) we could only do static. And the architecture is a bit weird for ssr.

S

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

But yea it needs a big rewrite to be able to work as SSR.
Basically its the same skeleton with different content/translations etc. And maybe some different "widgets"

1

1984 Ford Laser•11/11/25, 10:51 AM

I know how that is, we have a bunch of legacy clients who we have Joomla sites set up for. They are clunky but are pretty easy to template once you know what you're doing lol building a website in the Yootheme drag drop builder is far better than manually writing code any day though

S

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

Also it doesnt help when the initial skeleton was written by some juniors and now 90% of the website is a client component.
SSG does help here because it renders those and crawlers can index. But SSR on this will be a pain

Though reading the past responses, if you hit the 100 pages project limit - you may want Workers for

Similar Threads

Similar Threads

Similar Threads