[BUG]: Error: Failed to provision remote R2 bucket "<bucket>" for binding "NEXT_INC_CACHE_R2_BUCKET": Failed to check whether bucket exists: Premature close

[maloyuso]

Describe the bug

Hi! We started getting an error while deploying to cloudflare workers. We haven't performed changes to our Deployment process, but around 2:40 PM CST yesteday every cloudflare workers deploy started failing.

This is the error:
Error: Failed to provision remote R2 bucket "<bucket>" for binding "NEXT_INC_CACHE_R2_BUCKET": Failed to check whether bucket exists: Invalid response body while trying to fetch https://api.cloudflare.com/client/v4/accounts/***/r2/buckets/<bucket>: Premature close

Steps to reproduce

Build project with ISR support, try to deploy it

Expected behavior

Populating remote R2 incremental cache succeds and full deploy

@opennextjs/cloudflare version

1.19.1

Wrangler version

4.86.0

next info output

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.5.0: Mon Apr 27 20:41:15 PDT 2026; root:xnu-12377.121.6~2/RELEASE_ARM64_T6041
  Available memory (MB): 24576
  Available CPU cores: 14
Binaries:
  Node: 20.19.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: 10.33.0
Relevant Packages:
  next: 16.2.9 // Latest available version is detected (16.2.9).
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

Additional context

No response

[shreejalmaharjan-27]

For anyone else encountering the same issue here's how i fixed it..

Since that populate is optional (at runtime the worker hits R2 through the binding anyway), I just made it non-fatal with a pnpm patch on @opennextjs/cloudflare in dist/cli/commands/populate-cache.js:

const name = await resolveCacheName(incrementalCache);
try {
  switch (name) { /* ...existing cases... */ }
} catch (e) {
  if (populateCacheOptions.target === "remote") {
    logger.warn(`Remote incremental cache population failed, continuing. Cause: ${e instanceof Error ? e.message : String(e)}`);
  } else {
    throw e;
  }
}

After that it skips past the populate and wrangler versions upload runs fine.

[james-elicx]

fyi, looks like this was a regression in nodejs - nodejs/node#64004