Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Using the E2B JS SDK (v1.0.4) inside a Vercel Edge function threw SandboxError: 2: [unknown] Invalid redirect value, must be one of "follow" or "manual". The identical code ran fine on Node locally. The error came from the SDK's RPC layer (connect-es), which passed a redirect mode the Edge runtime does not implement — Edge fetch only supports "follow" and "manual", not "error".
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
The E2B team fixed Edge-runtime support in the JS SDK — it landed in v1.2.3 and up, where the API/RPC clients use redirect: "follow" (the only redirect mode Edge allows) for requests to E2B endpoints. Fix: upgrade with npm i e2b@^1.2.3. If you're stuck on an older SDK, the workaround is to run E2B calls on a regular non-edge (Node) runtime instead of Edge functions. Source: https://github.com/e2b-dev/E2B/issues/531
Fixes the E2B SandboxError "Invalid redirect value, must be one of follow or manual" on Vercel Edge by upgrading the E2B JS SDK to v1.2.3 or newer, where the RPC layer uses redirect: "follow".
Fixes the Cloudflare Workers TypeError 'Invalid redirect value, must be one of follow or manual' thrown when fetch is called with redirect: 'error'.
Fixes Terraform's "Error: Invalid reference ...