Skip to content

docs: clarify Cloudflare Access setup in populate-cache comment #1267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
petebacondarwin merged 1 commit into from
May 15, 2026
Merged

docs: clarify Cloudflare Access setup in populate-cache comment #1267

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions packages/cloudflare/src/cli/commands/populate-cache.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -406,11 +406,17 @@ async function sendEntryToR2Worker(options: {
"x-opennext-cache-key": key,
"content-length": fs.statSync(filename).size.toString(),
// Include Access Client ID and Secret if they are set in the environment,
// to allow the worker to authenticate with the Cloudflare API when writing to R2.
// so the helper worker can be reached through Cloudflare Access.
//
// The Application at "open-next-cache-populate.<account>.workers.dev" should have a policy with:
// - "Action" set to "Service Auth"
// - "Any Access Service Token" or "Service Token" + a specific service token
// If the workers.dev subdomain (or a parent route) is behind Cloudflare Access,
// attach a "Service Auth" policy to the *existing* Access application that already
// covers "open-next-cache-populate.<account>.workers.dev" — typically the
// "*.<account>.workers.dev" wildcard application. Creating a separate application
// scoped to this hostname has been observed to block the upload, even alongside
// the wildcard app. The policy should have:
// - Action set to "Service Auth"
// - An Include rule for "Any Access Service Token" or a specific Service Token
// See: https://opennext.js.org/cloudflare/cli#populating-remote-bindings-when-workers-are-protected-by-cloudflare-access
...(process.env.CLOUDFLARE_ACCESS_CLIENT_ID && process.env.CLOUDFLARE_ACCESS_CLIENT_SECRET
? {
"CF-Access-Client-Id": process.env.CLOUDFLARE_ACCESS_CLIENT_ID,
Expand Down
Loading