errorCallbackURL is not working it is ignored on error #744

@rohittiwari-dev commented on GitHub (Feb 27, 2025):

@Bekacru please help me on this its really important when it comes to maitaining a design system and neither i can modify default ui nor this feature is working

@rohittiwari-dev commented on GitHub (Feb 27, 2025): @Bekacru please help me on this its really important when it comes to maitaining a design system and neither i can modify default ui nor this feature is working

GiteaMirror commented

@rohittiwari-dev commented on GitHub (Feb 27, 2025):

Awsome thanks but when can this be released , i used better auth on production actually waiting for this fix

@rohittiwari-dev commented on GitHub (Feb 27, 2025): Awsome thanks but when can this be released , i used better auth on production actually waiting for this fix

GiteaMirror commented

@rohittiwari-dev commented on GitHub (Mar 2, 2025):

when using this

// Client Auth
import { createAuthClient } from "better-auth/react";
import { nextCookies } from "better-auth/next-js";

export const authClient = createAuthClient({
	baseURL: process.env.BETTER_AUTH_URL,
	plugins: [nextCookies()],
});

and doing social api call like

await authClient.signIn.social(
			{
				provider: "google",
				callbackURL: "/dashboard",
				errorCallbackURL: "/sign-in",
			},
			{
				onRequest: () => {
					setIsOAuthLogin(true);
				},
				onError: (ctx) => {
					setIsOAuthLogin(false);
					toast.error(ctx.error.message);
				},
			},
		);

it should redirect to errorCallbackURL right in v1.2.0

it is not redirecting
@Bekacru can you help me out

@rohittiwari-dev commented on GitHub (Mar 2, 2025): when using this ```typescript // Client Auth import { createAuthClient } from "better-auth/react"; import { nextCookies } from "better-auth/next-js"; export const authClient = createAuthClient({ baseURL: process.env.BETTER_AUTH_URL, plugins: [nextCookies()], }); ``` and doing social api call like ```typescript await authClient.signIn.social( { provider: "google", callbackURL: "/dashboard", errorCallbackURL: "/sign-in", }, { onRequest: () => { setIsOAuthLogin(true); }, onError: (ctx) => { setIsOAuthLogin(false); toast.error(ctx.error.message); }, }, ); ``` it should redirect to errorCallbackURL right in v1.2.0 it is not redirecting @Bekacru can you help me out

GiteaMirror commented

2026-03-13 08:02:35 -05:00

@rohittiwari-dev commented on GitHub (Mar 2, 2025):

@Bekacru ?

@rohittiwari-dev commented on GitHub (Mar 2, 2025): @Bekacru ?

GiteaMirror commented

@szilardx commented on GitHub (Apr 6, 2025):

I have this issue with 1.2.5 - setting errorCallbackURL not working using google social login.
Would it be possible to demonstrate proper usage on the nextjs demo?
Thank you!

@szilardx commented on GitHub (Apr 6, 2025): I have this issue with 1.2.5 - setting errorCallbackURL not working using google social login. Would it be possible to demonstrate proper usage on the nextjs demo? Thank you!

GiteaMirror commented

2026-03-13 08:02:35 -05:00

@ryuheechul commented on GitHub (Apr 16, 2025):

also experiencing errorCallbackURL being ignored on user canceling the sign in (with Google) with better-auth 1.2.7.

@ryuheechul commented on GitHub (Apr 16, 2025): also experiencing `errorCallbackURL` being ignored on user canceling the sign in (with Google) with _better-auth 1.2.7_.

GiteaMirror commented

2026-03-13 08:02:35 -05:00

@vinkovsky commented on GitHub (Apr 16, 2025):

same here

@vinkovsky commented on GitHub (Apr 16, 2025): same here

GiteaMirror commented

@stewones commented on GitHub (Jun 1, 2025):

same

@stewones commented on GitHub (Jun 1, 2025): same

GiteaMirror commented

@asynchroza commented on GitHub (Jun 6, 2025):

Any update here?

@asynchroza commented on GitHub (Jun 6, 2025): Any update here?

GiteaMirror commented

@asynchroza commented on GitHub (Jun 6, 2025):

After revisiting the PR which is supposedly closing this issue, I figured that the newly developed option only allows onAPIError which is a global endpoint for when the API route fails.

import {
    betterAuth
} from 'better-auth';
import { dialect } from '~/database/client';
import { env } from '~/env';

export const auth = betterAuth({
    socialProviders: {
        google: {
            clientId: env.GOOGLE_CLIENT_ID,
            clientSecret: env.GOOGLE_CLIENT_SECRET
        },
        facebook: {
            clientId: env.FACEBOOK_CLIENT_ID,
            clientSecret: env.FACEBOOK_CLIENT_SECRET
        }
    },
    database: dialect,
    onAPIError: {
        errorURL: "/login"
    }
});

This is not the preferred solution as this is a one stop solution for all flows which have authentication. In my particular case, if the user is logging in and they cancel the process, they are redirected to /login. That's fine but what if I have to reauthenticate a session in the background and something else happens? Why can't we just make the errorCallbackUrl work?

@asynchroza commented on GitHub (Jun 6, 2025): After revisiting the PR which is supposedly closing this issue, I figured that the newly developed option only allows `onAPIError` which is a global endpoint for when the API route fails. ```ts import { betterAuth } from 'better-auth'; import { dialect } from '~/database/client'; import { env } from '~/env'; export const auth = betterAuth({ socialProviders: { google: { clientId: env.GOOGLE_CLIENT_ID, clientSecret: env.GOOGLE_CLIENT_SECRET }, facebook: { clientId: env.FACEBOOK_CLIENT_ID, clientSecret: env.FACEBOOK_CLIENT_SECRET } }, database: dialect, onAPIError: { errorURL: "/login" } }); ``` This is not the preferred solution as this is a one stop solution for all flows which have authentication. In my particular case, if the user is logging in and they cancel the process, they are redirected to `/login`. That's fine but what if I have to reauthenticate a session in the background and something else happens? Why can't we just make the `errorCallbackUrl` work?

GiteaMirror commented

@H7ioo commented on GitHub (Jun 24, 2025):

Having the same issues.
When user gets banned and tries to login with OAuth, the user gets redirected to api/auth/error instead of specified redirect page

@H7ioo commented on GitHub (Jun 24, 2025): Having the same issues. When user gets banned and tries to login with OAuth, the user gets redirected to api/auth/error instead of specified redirect page

GiteaMirror commented

@irg1008 commented on GitHub (Jul 2, 2025):

In mi case the onError callback doesn't even get triggered

@irg1008 commented on GitHub (Jul 2, 2025): In mi case the onError callback doesn't even get triggered

GiteaMirror commented

@staguer commented on GitHub (Jul 2, 2025):

I'm also running into this issue.

@staguer commented on GitHub (Jul 2, 2025): I'm also running into this issue.

GiteaMirror commented

@H7ioo commented on GitHub (Jul 2, 2025):

This should be solved in the next version (1.3.0) you can check the releases page.

@H7ioo commented on GitHub (Jul 2, 2025): This should be solved in the next version (1.3.0) you can check the releases page.

GiteaMirror commented

@esoteloferry commented on GitHub (Aug 10, 2025):

Having the same issues. When user gets banned and tries to login with OAuth, the user gets redirected to api/auth/error instead of specified redirect page

I encountered same issue, and using 1.3.4 still does not fix , what workaround did you use?

@esoteloferry commented on GitHub (Aug 10, 2025): > Having the same issues. When user gets banned and tries to login with OAuth, the user gets redirected to api/auth/error instead of specified redirect page I encountered same issue, and using 1.3.4 still does not fix , what workaround did you use?

GiteaMirror commented

@erquhart commented on GitHub (Aug 14, 2025):

Confirmed this url doesn't get called if, for example, you start Google log in and hit cancel instead of approving the connection.

@erquhart commented on GitHub (Aug 14, 2025): Confirmed this url doesn't get called if, for example, you start Google log in and hit cancel instead of approving the connection.

GiteaMirror commented

@JackNeto commented on GitHub (Aug 22, 2025):

Any update on this. Not sure why this issue is closed

@JackNeto commented on GitHub (Aug 22, 2025): Any update on this. Not sure why this issue is closed

GiteaMirror commented

@najibghadri commented on GitHub (Sep 3, 2025):

Needs reopening guys.. @ping-maxwell

@najibghadri commented on GitHub (Sep 3, 2025): Needs reopening guys.. @ping-maxwell

GiteaMirror commented

@v1taly commented on GitHub (Sep 6, 2025):

Need reopening. Still doesn't work.

@v1taly commented on GitHub (Sep 6, 2025): Need reopening. Still doesn't work.

GiteaMirror commented