cloudflare error

Hello - I have a sveltekit application which is hosted on cloudflare pages.

I am using google social login, and it works fine in development.

but in prod, it gives me 500 error right after I click on google account

cookies are not set, and I get this in my cloudflare log:

"message": [
"# SERVER_ERROR: ",
"Error: Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler. This is a limitation of Cloudflare Workers which allows us to improve overall performance. (I/O type: Writable)"
]

What might be happening? How can I get this working?

dimsumhamOP•4/3/25, 4:34 PM

update - did a fresh project and still getting same issue.

dimsumhamOP•4/3/25, 4:34 PM

@bekacru for what it's worth - been trying my best to get to the bottom of the issue, and says this is it? does it make any sense?

dimsumhamOP•4/3/25, 6:19 PM

Ddimsumham Hello - I have a sveltekit application which is hosted on cloudflare pages. I ...

bekacru•4/3/25, 6:19 PM

This usually happens when you try to aaccess same context in 2 differnt places. It's not better auth specific problem

dimsumhamOP•4/3/25, 6:19 PM

sorry i just see you typing - got an update

dimsumhamOP•4/3/25, 6:19 PM

so it seems like the issue has to do with kyselyAdapter

dimsumhamOP•4/3/25, 6:19 PM

this is my auth.ts set up

dimsumhamOP•4/3/25, 6:19 PM

dimsumhamOP•4/3/25, 6:20 PM

when i deploy without kyselyAdapter - just running in memory, it works fine.

bekacru•4/3/25, 6:21 PM

first type should be "postgres"

Ddimsumham so it seems like the issue has to do with kyselyAdapter

bekacru•4/3/25, 6:22 PM

it might have something to do with how env is resovled in cf workers

dimsumhamOP•4/3/25, 6:26 PM

if it's env resolving shouldn't it still throw an error without kyselyAdapter since the GOOGLE_CLIENT_ID / SECRET resolves in the same call?

dimsumhamOP•4/3/25, 10:08 PM

Update - not just kyselyadapter. Seems to be happening with any sort of database writes, even with the most vanilla code.

this is my set up - still having same issues. Every time, at callback URL stage, it errors out. Either with I/O error, or "this code will never generate a response" error.

One other thing to mention is that I'm using an auth database that's sitting on a vps but not sure if that matters?

Bbekacru it might have something to do with how env is resovled in cf workers

dimsumhamOP•4/3/25, 10:15 PM

Also, confirm it's not the env variables access. Error still happens even if I hard code it in.

Ddimsumham Update - not just kyselyadapter. Seems to be happening with any sort of database...

bekacru•4/3/25, 10:16 PM

Im not sure what you can do to fix it but it seems like it's caused by the db connection being used outside of the handler context

Bbekacru Im not sure what you can do to fix it but it seems like it's caused by the db co...

dimsumhamOP•4/3/25, 10:20 PM

Is there a recommended set up for cloudflare/serverless deployment where both client and server auth sits with the serverless provider, and database is remote?

dimsumhamOP•4/3/25, 10:20 PM

Or any other combo of solutions to get around this

dimsumhamOP•4/3/25, 10:21 PM

If it helps at all - when I literally just enter the callback url again into the address bar it works.

dimsumhamOP•4/4/25, 4:25 PM

Update: cloned better-auth repo, added some logs, and running it locally using wrangler pages dev.

Seems like this is the issue.

will continue investigating and report back.

dimsumhamOP•4/4/25, 5:29 PM

Update: not a good, but still a solution is to wrap betterAuth around in a function and call that.

stu•4/8/25, 1:06 PM

Hey @dimsumham I'm getting the same error. Did you find any clean way to resolve, or should I wrap auth in a function? I'm also using postgres.

dimsumhamOP•4/8/25, 1:07 PM

Wrapping in a function is the cleanest and easiest way to resolve this issue.

If you're worried about performance / overwhelming auth server then you could use hyperdrive or a pooler on database side.

stu•4/8/25, 1:09 PM

Nice, I'm new to Cloudflare, so just trying to get things working. I'll look into Hyperdrive, sounds like a good fit for using Postgres with Cloudflare.

dimsumhamOP•4/8/25, 1:34 PM

Yeah the V8 isolate environment is pain in the ass to deal with but its so worth it

stu•4/13/25, 12:31 AM

hey @dimsumham, was curious if you had success using Cloudflare + Hyperdrive + better-auth?

Basically, I have sign-in functionality server-side like:

    const result = await auth(env).api.signInEmail({
      body: {
        email: email.toString(),
        password: password.toString(),
      },
      asResponse: true,
    });

    const result = await auth(env).api.signInEmail({
      body: {
        email: email.toString(),
        password: password.toString(),
      },
      asResponse: true,
    });

But it's hanging forever when I hit it. No logs, just forever loading.

Auth looks like:

  export const auth = (env: Env) =>
    betterAuth({
      database: {
        dialect: new PostgresJSDialect({
          postgres: getDb(env), // Call getDb() as a function to create a new connection each time
        }),
        // dialect,
        type: "postgres",
      },
      emailAndPassword: {
        // email and password stuff
      },
      secret: BETTER_AUTH_SECRET,
    });

  export const auth = (env: Env) =>
    betterAuth({
      database: {
        dialect: new PostgresJSDialect({
          postgres: getDb(env), // Call getDb() as a function to create a new connection each time
        }),
        // dialect,
        type: "postgres",
      },
      emailAndPassword: {
        // email and password stuff
      },
      secret: BETTER_AUTH_SECRET,
    });

And getDb function looks like:

export function getDb(env: Env) {
  // Connection URL from environment variables
  let connectionString = env.HYPERDRIVE.connectionString;

  const sql = postgres(connectionString, {
    max: 5,
    // idle_timeout: 30,
    ssl: import.meta.env.DEV,
    // Debug options - remove in production
    debug: true,
    fetch_types: false,
  });

  return sql;
}

export function getDb(env: Env) {
  // Connection URL from environment variables
  let connectionString = env.HYPERDRIVE.connectionString;

  const sql = postgres(connectionString, {
    max: 5,
    // idle_timeout: 30,
    ssl: import.meta.env.DEV,
    // Debug options - remove in production
    debug: true,
    fetch_types: false,
  });

  return sql;
}

Any ideas the changes I should make?

dimsumhamOP•4/13/25, 12:53 AM

Let me take a look tonight / tomorrow. I had an issue with this but did manage to get something working

dimsumhamOP•4/13/25, 1:06 AM

In your connection string - are you using any suffix? For schema etc

stu•4/13/25, 1:09 AM

Amazing, thanks. Yes, the hyperdrive connection string has

postgresql://

postgresql://

at the beginning.

It's working in other instances, for example to fetch data.

But it's getting stuck specifically with better-auth requests I think.

export const auth = (env: Env) => betterAuth({ database: { dialect: new PostgresJSDialect({ postgres: getDb(env), // Call getDb() as a function to create a new connection each time }), // dialect, type: "postgres", }, emailAndPassword: { // email and password stuff }, secret: BETTER_AUTH_SECRET, });

export function getDb(env: Env) { // Connection URL from environment variables let connectionString = env.HYPERDRIVE.connectionString; const sql = postgres(connectionString, { max: 5, // idle_timeout: 30, ssl: import.meta.env.DEV, // Debug options - remove in production debug: true, fetch_types: false, }); return sql; }

cloudflare error

Similar Threads

Similar Threads

Similar Threads