Better Auth•2mo ago

Running SvelteKit on Cloudflare workers I am getting this error

[Better Auth]:\u001b[0m INTERNAL_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)

[Better Auth]:\u001b[0m INTERNAL_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)

via /api/auth/token inside onSuccess on sign-in

23 Replies

Unknown User•2mo ago

Message Not Public

CoryOP•2mo ago

No idea, this is my code

    const handleSignin = async () => {
        await authClient.signIn.email(
            {
                email: $formData.email,
                password: $formData.password
            },
            {
                onSuccess: async (ctx) => {
                    // Redirect to dashboard
                    const redirectUri = page.url.searchParams.get('redirect_uri');

                    const res = await fetch('/api/auth/token', {
                        headers: {
                            Authorization: `Bearer ${ctx.data.token}`
                        }
                    });

                    // Cache the json web token
                    const tokenData = (await res.json()) as { token: string } | undefined;

                    if (tokenData) {
                        Cookies.set('jwt', tokenData.token, {
                            path: '/',
                            expires: new Date(Date.now() + 30 * 24 * 60 * 60 * 1000)
                        });
                    }

                    goto(redirectUri ?? '/');
                },
            }
        );
    };

    const handleSignin = async () => {
        await authClient.signIn.email(
            {
                email: $formData.email,
                password: $formData.password
            },
            {
                onSuccess: async (ctx) => {
                    // Redirect to dashboard
                    const redirectUri = page.url.searchParams.get('redirect_uri');

                    const res = await fetch('/api/auth/token', {
                        headers: {
                            Authorization: `Bearer ${ctx.data.token}`
                        }
                    });

                    // Cache the json web token
                    const tokenData = (await res.json()) as { token: string } | undefined;

                    if (tokenData) {
                        Cookies.set('jwt', tokenData.token, {
                            path: '/',
                            expires: new Date(Date.now() + 30 * 24 * 60 * 60 * 1000)
                        });
                    }

                    goto(redirectUri ?? '/');
                },
            }
        );
    };

CoryOP•2mo ago

I think it has something to do with fetching?

CoryOP•2mo ago

trying to figure out from other people getting the error in cloudflare discord

Unknown User•2mo ago

Message Not Public

CoryOP•2mo ago

I am using SvelteKit, not nextjs What would the bearer plugin do for me?

Unknown User•2mo ago

Message Not Public

CoryOP•2mo ago

That’s correct but the JWT plugin requires a token which you can just get from the returned context in this instance I ended up moving the JWT generation to the backend and setting cookies there as well, will try cloud flare later today to see if that helps at all Sadly I am still getting the odd cloudflare error @bekacru Any idea what could be causing this Cloudflare error? This is bizzare one I am not sure how to fix - or is there any way to see exactly what aspect of better-auth is causing this? Is there some debug mode? I wonder if it's something to do with running

  const session = await auth.api.getSession({
    headers: request.headers
});

  const session = await auth.api.getSession({
    headers: request.headers
});

within svelteKitHandle? I think it may be failing at "get-session"

bekacru•2mo ago

are you trying to call this from the sever?

CoryOP•2mo ago

No that was on the client

bekacru•2mo ago

I'm not familiar with the error either. Have you tried removing the onSuccess hook?

CoryOP•2mo ago

Yea it’s not just with sign-in. Seems to happen whenever “get-session” is called but not 100%z Honestly I am wondering if this is a cloudflare issue or something I mean something that changed on cloudflares end

bekacru•2mo ago

the error is saying a context is share between 2 handlers but better auth won't be able to do that unless there is some mis confiugration or something is going on between the sveltekit adapter and cf.

CoryOP•2mo ago

Yea Well here is my hooks code, if you don't mind combing over it, does it look fine to you?

const authHandle: Handle = async ({ event, resolve }) => {
    const { locals, request } = event;

    if (event.route.id?.includes('(app)')) {
        // Refresh or get the existing session
        const session = await auth.api.getSession({
            headers: request.headers
        });

        // Handle unauthenticated users
        if (!session) {
            // Redirect to login page for app routes
            throw redirectToLogin(event.url);
        }

        // SUCCESS - User has been authenticated.
        // Pass the user and session to locals so it can be easily access in endpoints and server side events
        locals.session = session.session;
        locals.user = session.user;

        // If the user email is not verified and they are not already
        // on the verification page, redirect them
        if (!event.route.id?.includes('email-verification') && !session.user.emailVerified) {
            redirect(302, route('/email-verification'));
        }
    }

    return svelteKitHandler({ event, resolve, auth });
};

const svelteKitHandle: Handle = async ({ event, resolve }) => {
  ...
}

export const handle = sequence(authHandle, svelteKitHandle);

const authHandle: Handle = async ({ event, resolve }) => {
    const { locals, request } = event;

    if (event.route.id?.includes('(app)')) {
        // Refresh or get the existing session
        const session = await auth.api.getSession({
            headers: request.headers
        });

        // Handle unauthenticated users
        if (!session) {
            // Redirect to login page for app routes
            throw redirectToLogin(event.url);
        }

        // SUCCESS - User has been authenticated.
        // Pass the user and session to locals so it can be easily access in endpoints and server side events
        locals.session = session.session;
        locals.user = session.user;

        // If the user email is not verified and they are not already
        // on the verification page, redirect them
        if (!event.route.id?.includes('email-verification') && !session.user.emailVerified) {
            redirect(302, route('/email-verification'));
        }
    }

    return svelteKitHandler({ event, resolve, auth });
};

const svelteKitHandle: Handle = async ({ event, resolve }) => {
  ...
}

export const handle = sequence(authHandle, svelteKitHandle);

bekacru•2mo ago

I think sequence is the problem maybe. I'm not sure what it is but it seems like it's sharing the request context.

CoryOP•2mo ago

Interesting. Shouldn't it share request context? I thought that was the point

bekacru•2mo ago

yeah on CF. you just need to export the handler without sequence

CoryOP•2mo ago

Ok I'll try Still the same issue unfortunately Something on every request is going on I wonder if it's the drizzle adapter somehow? Maybe drizzle-orm/postgres-js Interesting, switching to node-postgres seems to get rid of the error but now I am getting another error

CoryOP•2mo ago

ugh Well either way this does not seem like a better-auth error so I will figure it out Hm I wonder if this is related?

CoryOP•2mo ago

https://github.com/better-auth/better-auth/issues/969

GitHub

Cloudflare: Error: The script will never generate a response. · Iss...

Is this suited for github? Yes, this is suited for github To Reproduce Deploy or preview an aplication using Cloudlflare Pages or Workers, the issue does not show up if you use dev Try to sign in C...

CoryOP•2mo ago

@bekacru I think this is promising

Gaming

Programming

Running SvelteKit on Cloudflare workers I am getting this error

Did you find this page helpful?