Infinite redirect loop in NextJS development environment #1436

ghost · 2023-06-29T16:50:34Z

dimkl · 2023-06-29T18:31:26Z

Hello @Aayushpatil77 and thank you for opening this issue.
If the issue is not resolved after trying the 3 Reasons described in the error message, could you provide a repository that reproduces this error to investigate it more and get back to you?

adarsh-gupta101 · 2023-06-30T16:46:04Z

Same issue here.

Using Next.js and getting an infinite redirect. But when we refresh the page again, it will work as expected.

GitHub repo example->https://github.com/adarsh-gupta101/Next-full-stack-editor

ghost · 2023-06-30T16:51:01Z

@dimkl
Github repo :- https://github.com/Aayushpatil77/ecommerce-dashboard

GuillaumeDesforges · 2023-07-03T23:08:20Z

Had sort of the same issue. It works fine on localhost, but when I try to proxy (e.g. using ngrok) the browser gets stuck in an infinite loop. In my case, React does not display any error message.

I tried to run the debugger in Chrome; found this line to be the "culprit":
https://github.com/clerkinc/javascript/blob/019992f2063ba8580446edf98c760eabcc8fc71a/packages/backend/src/tokens/interstitial.ts#L101-L102

Why would my page suddenly have an empty fragment? I would expect that it is added in the call itself e.g.

-                        window.location.href = window.location.href;
+                        window.location.href = window.location.href + "#";

GuillaumeDesforges · 2023-07-03T23:16:34Z

This was with version @clerk/nextjs==4.19.0, seems fixed in @clerk/nextjs==4.21.13

nkeil · 2023-07-10T19:18:23Z

I got this error after switching auth providers to Clerk, I got it to work by clearing my old cookies.

ValkovMirec · 2023-07-14T13:40:36Z

I got the same problem. Fresh install of T3, installed clerk, followed quick start docs, first npm run dev and i got this error. Tried everything. Skewing time updating, checked keys. It doesn't work

aviroopjana · 2023-08-05T21:43:13Z

This was with version @clerk/nextjs==4.19.0, seems fixed in @clerk/nextjs==4.21.13

I am using "@clerk/nextjs": "^4.23.2" this version and still getting the error... If anyone knows how to fix it please do let me know

catchshyam · 2023-08-06T13:09:56Z

On my windows PC, syncing with the time server solved the issue. It might occur again, but I am good for now

aviroopjana · 2023-08-06T17:07:00Z

Yeah it also worked for me

satishkumarsajjan · 2023-08-07T12:40:31Z

I am facing the same issue as of now. It was working fine the day before i was developing the app. when i ran the Next app again the next day, it's showing the infinite loop error. Is their any particular reason??

satishkumarsajjan · 2023-08-07T12:45:22Z

Clerk needs your system clock to be in sync with your current timezone. I synced my system timezone correctly. The clerk is working fine.

aviroopjana · 2023-08-07T12:48:20Z

Clerk needs your system clock to be in sync with your current timezone. I synced my system timezone correctly. The clerk is working fine.

Yeah that was the problem

OkolieOKS234 · 2023-08-07T14:17:32Z

Tried syncing my time, still the same issue

royanger · 2023-08-08T00:10:24Z

If you are experiencing this in NextJS, please add debug: true to your authMiddleware. See https://clerk.com/docs/nextjs/middleware#middleware-argument-types. This will give you debugging loads which can produce more information.

If you see an error like the one below, then it is indicating your clock is out of sync.

[0] "message": "JWT issued at date claim (iat) is in the future. Issued at date: Mon Jul 10 2023 19:40:49 GMT+0200 (Central European Summer Time); Current date: Mon Jul 10 2023 19:40:38 GMT+0200 (Central European Summer Time); (reason=token-not-active-yet, token-carrier=cookie)"

creative-tutorials · 2023-08-12T14:37:55Z

When I try clearing the cookies it works for me, but after saving a few changes to my code, it doesn't work anymore

GitHub Repo --> https://github.com/creative-tutorials/resubase

creative-tutorials · 2023-08-12T14:42:06Z

If you are experiencing this in NextJS, please add debug: true to your authMiddleware. See https://clerk.com/docs/nextjs/middleware#middleware-argument-types. This will give you debugging loads which can produce more information.

If you see an error like the one below, then it is indicating your clock is out of sync.

[0] "message": "JWT issued at date claim (iat) is in the future. Issued at date: Mon Jul 10 2023 19:40:49 GMT+0200 (Central European Summer Time); Current date: Mon Jul 10 2023 19:40:38 GMT+0200 (Central European Summer Time); (reason=token-not-active-yet, token-carrier=cookie)"

Thanks for the tip, it shows much clearer information now, the state for isSignedIn seems to be treated as false, with a JWT message

royanger · 2023-08-13T00:00:03Z

Issued at date: Mon Jul 10 2023 19:40:49 GMT+0200 (Central European Summer Time); Current date: Mon Jul 10 2023 19:40:38 GMT+0200 (Central European Summer Time); (reason=token-not-active-yet, token-carrier=cookie)

This is confirming that your clock is out of sync and in the future. Syncing your clock with a time server should resolve this error.

creative-tutorials · 2023-08-13T00:11:06Z

Issued at date: Mon Jul 10 2023 19:40:49 GMT+0200 (Central European Summer Time); Current date: Mon Jul 10 2023 19:40:38 GMT+0200 (Central European Summer Time); (reason=token-not-active-yet, token-carrier=cookie)

This is confirming that your clock is out of sync and in the future. Syncing your clock with a time server should resolve this error.

Thank you very much, it turns out that toggling "Set time automatically" and "Set time zone automatically", with synchronizing the time, and properly setting my time zone did the trick.

IAmTahazzot · 2023-08-19T06:03:04Z

On my windows PC, syncing with the time server solved the issue. It might occur again, but I am good for now

Does anybody encounter it on production app? where end users doesn't sync with time server from windows settings?
I mean, We developer fixing it on our device but what if it happens same with end users ? Where they didn't sync with time server?

(Mine also fixed with time server sync)

creative-tutorials · 2023-08-19T07:52:40Z

On my windows PC, syncing with the time server solved the issue. It might occur again, but I am good for now

Does anybody encouter it on production app? where use doesn't sync with time server from windows settings? I mean, We developer fixing it on our device but what if it happens same with end users ? Where they didn't sync with time server?

(Mine also fixed with time server sync)

Yikes, you're definitely right about that, there has to be like a workaround around this.

emLuc86dev · 2023-08-19T23:55:47Z

I am using "@clerk/nextjs": "^4.23.2". I have changed the time and time zone and I still getting the same error ... Does anyone have a solutions?

kachar · 2023-08-20T06:47:43Z

We've noticed. that certain users have bad cookie values which causes the infinite loop.

The cookie name is __client_uat and the bad value is 0 instead of some timestamp like 1692272951

Once we clear this cookie the redirect loops are gone.

Our observation of this cookie is that it gets a bad value when we switch between the subdomains of our app - Production / Staging.

creative-tutorials · 2023-08-20T17:46:19Z

We've noticed. that certain users have bad cookie values which causes the infinite loop.

The cookie name is __client_uat and the bad value is 0 instead of some timestamp like 1692272951

Once we clear this cookie the redirect loops are gone.

Our observation of this cookie is that it gets a bad value when we switch between the subdomains of our app - Production / Staging.

I didn't get this bad value, All I needed was to change the time zone. Thanks for sharing by the way

creative-tutorials · 2023-08-20T17:49:09Z

I am using "@clerk/nextjs": "^4.23.2". I have changed the time and time zone and I still getting the same error ... Does anyone have a solutions?

Which OS are you using If I may ask @emLuc86dev

emLuc86dev · 2023-08-20T23:08:00Z

I"m using Windows 11. I changed my time and time zone. I cleared the cache and cookies and I'm still getting the same error. Then I tried another web browser and still the same... Thanks for your time El dom, 20 de ago de 2023 1:49 p. m., Timi ***@***.***> escribió:

…

I am using ***@***.***/nextjs": "^4.23.2". I have changed the time and time zone and I still getting the same error ... Does anyone have a solutions? Which OS are you using If I may ask? — Reply to this email directly, view it on GitHub <#1436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUXR5LLQAMTKQI4F4D5HM43XWJE2DANCNFSM6AAAAAAZYYYU6Q> . You are receiving this because you commented.Message ID: ***@***.***>

stx-chris · 2024-01-15T19:10:08Z

We are experiencing the exact same error since releasing our production environment. The issue might be tied to the __client_uat cookie which is available twice if both the develop and the main instance are running on the same domain.

We have the following scenario:

development on a.b.c.mysite.io
main on app.mysite.io

This is the cookie we see on main:

__client_uat = <timestamp>

This is what we see on develop:

First cookie, domain "a.b.c.mysite.io": __client_uat = <timestamp>
Second cookie, domain ".mysite.io": __client_uat = 0

Once one has visited the main site with their browser and switches to develop to test something, the site is trapped in an infinite loop with the error referring to the said cookie, ie.

The Cookie '__client_uat' has been rejected for invalid domain.

We have to painfull clear the cookies, refresh everything and refrain from accessing the live site in the same session. It never occurs on localhost. Anybody else having this issue?

(Node v18.17.0, @clerk/nextjs v4.29.3, in Docker)

carlelgstroem · 2024-01-22T00:53:19Z

I just ran into the same issue after updating my node to v.21. I resolved the issue by downgrading node to v.18 and updating nextjs to v.14.1.0. Hope this might help someone!

creative-tutorials · 2024-01-26T11:30:31Z

I just ran into the same issue after updating my node to v.21. I resolved the issue by downgrading node to v.18 and updating nextjs to v.14.1.0. Hope this might help someone!

This will help a lot. Thanks!

But I want to know who else is still having this issue. I'm on node v.20.10.0 and I haven't noticed these issues for a long time, it comes back yes, but when I sync my time, I don't notice it again. The issue only comes back whenever I run into a low battery on my laptop.

eraoul · 2024-01-29T04:51:10Z

I'm running into this on node v21.6.1

creative-tutorials · 2024-01-29T12:50:31Z

I'm running into this on node v21.6.1

Try syncing your clock please

flean · 2024-01-31T19:39:01Z

I just ran into the same issue after updating my node to v.21. I resolved the issue by downgrading node to v.18 and updating nextjs to v.14.1.0. Hope this might help someone!

This will help a lot. Thanks!

But I want to know who else is still having this issue. I'm on node v.20.10.0 and I haven't noticed these issues for a long time, it comes back yes, but when I sync my time, I don't notice it again. The issue only comes back whenever I run into a low battery on my laptop.

We are also having this issue. Still have no clue how to fix it.

jameslporter · 2024-01-31T19:46:39Z

This is due to clerk not supporting multiple instances on the same host/domain name. I've asked clerk to call it out in the docs to avoid confusion. They have a future feature planned that would support instances across subdomain. Use another hostname and you won't hit the infinite redirect.

…

On Wed, Jan 31, 2024, 1:39 PM Rey ***@***.***> wrote: I just ran into the same issue after updating my node to v.21. I resolved the issue by downgrading node to v.18 and updating nextjs to v.14.1.0. Hope this might help someone! This will help a lot. Thanks! But I want to know who else is still having this issue. I'm on node v.20.10.0 and I haven't noticed these issues for a long time, it comes back yes, but when I sync my time, I don't notice it again. The issue only comes back whenever I run into a low battery on my laptop. We are also having this issue. Still have no clue how to fix it. — Reply to this email directly, view it on GitHub <#1436 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAG5UFXJ6CHKZPPCU2GUKDYRKMWDAVCNFSM6AAAAAAZYYYU6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJZHAYDKNRWG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

eraoul · 2024-01-31T22:38:58Z

@jameslporter yes I just figured out it must be something like that. I was running prod on mydomain.com and a staging instance on a subdomain, staging.mydomain.com. This caused the infinite loop. I found out that if I cleared my cookies etc. in Chrome and then viewed the subdomain, it would work (at least for a while), but once I viewed the prod instance things would be screwed up again.

Great to hear there is future work planned to support this across subdomains; would rather not have to pay for extra domains just to support a staging environment (unless that's a best practice for some reason etc.)

dnyn92 · 2024-02-14T21:42:41Z

For me upgrading to @clerk/nextjs=4.29.7,next=14.0.4 did not help, but eventually clearing cookies and localstorage did

alamenai · 2024-03-09T21:58:03Z

@dimkl Github repo :- https://github.com/Aayushpatil77/ecommerce-dashboard

Not found!

alamenai · 2024-03-09T21:58:38Z

For me upgrading to @clerk/nextjs=4.29.7,next=14.0.4 did not help, but eventually clearing cookies and localstorage did

It happened only in development or even the production?

dnyn92 · 2024-03-14T18:57:04Z

For me upgrading to @clerk/nextjs=4.29.7,next=14.0.4 did not help, but eventually clearing cookies and localstorage did

It happened only in development or even the production?

It only helped for the initial page load but same issue after I refreshed. I have figured out the final fix now. Seem to be a Nextjs Issue. Upgrading to 14.1.3 solved the issue eventually. vercel/next.js#55648

creative-tutorials · 2024-03-22T15:22:18Z

Mainly

For me upgrading to @clerk/nextjs=4.29.7,next=14.0.4 did not help, but eventually clearing cookies and localstorage did

It happened only in development or even the production?

It only helped for the initial page load but same issue after I refreshed. I have figured out the final fix now. Seem to be a Nextjs Issue. Upgrading to 14.1.3 solved the issue eventually. vercel/next.js#55648

Mainly everyone should just upgrade to Next.js 14.1.3. It worked for me as I upgraded as well.

yuvrajzingh · 2024-04-14T11:14:46Z

Mainly

For me upgrading to @clerk/nextjs=4.29.7,next=14.0.4 did not help, but eventually clearing cookies and localstorage did

It happened only in development or even the production?

It only helped for the initial page load but same issue after I refreshed. I have figured out the final fix now. Seem to be a Nextjs Issue. Upgrading to 14.1.3 solved the issue eventually. vercel/next.js#55648

Mainly everyone should just upgrade to Next.js 14.1.3. It worked for me as I upgraded as well.

Yes, upgrading my Next.js ('^14.2.1') worked for me. Just do npm install next@latest and it should install the latest Next.js which should resolve this issue with clerk.

nikos-pblworks · 2024-04-23T13:28:02Z

We are experiencing the exact same error since releasing our production environment. The issue might be tied to the __client_uat cookie which is available twice if both the develop and the main instance are running on the same domain.

We have the following scenario:

development on a.b.c.mysite.io

main on app.mysite.io

This is the cookie we see on main:

__client_uat = <timestamp>

This is what we see on develop:

First cookie, domain "a.b.c.mysite.io": __client_uat = <timestamp>

Second cookie, domain ".mysite.io": __client_uat = 0

Once one has visited the main site with their browser and switches to develop to test something, the site is trapped in an infinite loop with the error referring to the said cookie, ie.

The Cookie '__client_uat' has been rejected for invalid domain.

We have to painfull clear the cookies, refresh everything and refrain from accessing the live site in the same session. It never occurs on localhost. Anybody else having this issue?

(Node v18.17.0, @clerk/nextjs v4.29.3, in Docker)

Same issue here. @stx-chris did you figure out a solution? Was it solved by updating to the latest packages?

alamenai · 2024-04-30T22:54:47Z

Hi guys, I figured out that the issue is related to the local storage and session's keys. When I delete them it works as expected. I guess this happens when the authentication failed. This is my only for my case.

hieutrluu · 2024-05-07T05:08:53Z

I got into redirect loop with these packages
clearning localstorage and session keys does not help

"next": "^14.2.3",
"@clerk/nextjs": "4.30.1",

jescalan · 2024-05-07T17:30:26Z

@hieutrluu Could you please open a new issue or reach out to support@clerk.dev with a minimal reproduction? Thank you!

Vipigal · 2024-05-13T01:41:35Z

I found a rather dumb reason why I was being infinitly redirected in my end. In the middleware.ts setup, I had my RouteMatcher configured like so:

import { NextResponse } from "next/server";

const isProtectedRoute = createRouteMatcher(["/(.*)"]);

export default clerkMiddleware((auth, req) => {
  if (isProtectedRoute(req)) {
    auth().protect();
  }

  return NextResponse.next();
});

export const config = {
  matcher: ["/((?!.+.[w]+$|_next).*)", "/", "/(api|trpc)(.*)"],
};

The problem was that the createRouteMatcher method was configured to redirect every path starting with "/", which Im assuming included the /sign-up page and created the loop.

Changing the line to const isProtectedRoute = createRouteMatcher(["/"]); fixed my problem.

(I added the wildcard cause I wanted to make every route private, seems I might have to find another way...)

creative-tutorials · 2024-05-13T06:27:46Z

Everyone has different ways on how to solve this issue, mainly I'd just upgrade all my packages to latest, and make sure my date-and-time are correct

i-am-chitti · 2024-08-18T17:51:41Z

I faced the redirect issue due to middleware. Make sure, you include the sign in/sign up path in public path routes. Next, redirect won't happen anymore.

const isPublicRoute = createRouteMatcher(['/agency/sign-in(.*)', '/agency/sign-up(.*)', '/_next(.*)'])

DevTaehong · 2024-10-01T13:43:06Z

Clerk needs your system clock to be in sync with your current timezone. I synced my system timezone correctly. The clerk is working fine.

On my Windows machine, I turned off set time zone automatically and set time automatically and it worked...!!!

g-wozniak · 2024-12-12T15:28:16Z

So my users will need to sync their clock to the timezone or it's just happening for development?

Vipigal · 2024-12-13T01:39:22Z

Only in development. If your users have a misconfigured clock chances are that they are having problems accessing all types of web pages.

…

________________________________ From: Greg Wozniak ***@***.***> Sent: Thursday, December 12, 2024 12:28:44 PM To: clerk/javascript ***@***.***> Cc: Vinicius Pinho ***@***.***>; Comment ***@***.***> Subject: Re: [clerk/javascript] Infinite redirect loop in NextJS development environment (Issue #1436) So my users will need to sync their clock to the timezone or it's just happening for development? — Reply to this email directly, view it on GitHub<#1436 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXFVS2LBV7K5TSYE2QE34GL2FGTSZAVCNFSM6AAAAAAZYYYU6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZZGI4DMOJXGY>. You are receiving this because you commented.Message ID: ***@***.***>

zohairhadi · 2025-02-06T06:28:48Z

im getting the same error again with "next": "15.1.2" and "@clerk/nextjs": "^6.8.1"

jescalan · 2025-02-07T22:43:18Z

I am locking this conversation now.

If you are having issues with Clerk, please reach out to our support and one of our dedicated staff will help get your issue resolved. I don't want anyone to end up posting a problem here expecting help, and it never gets answered, as our support team does not actively monitor closed github discussions.

wobsoriano mentioned this issue Jul 2, 2023

Infinite reload on localhost wobsoriano/nuxt-clerk-template#1

Closed

dimkl changed the title ~~Infinite redirect loop~~ Infinite redirect loop in NextJS development environment Jul 7, 2023

dimkl added the interstitial label Aug 1, 2023

gerald-lbn mentioned this issue Aug 8, 2023

state is interstitial, reason: cross-origin-referrer #1566

Closed

5 tasks

stx-chris mentioned this issue Jan 16, 2024

Infinite redirect loop on same-domain deployments #2595

Closed

4 tasks

cameronapak mentioned this issue Jun 3, 2024

ERR_TOO_MANY_REDIRECTS Bug panteliselef/astro-with-clerk-auth#167

Open

dct0 mentioned this issue Aug 16, 2024

Fix staging deployments codersforcauses/website#1548

Open

clerk locked as resolved and limited conversation to collaborators Feb 7, 2025

Infinite redirect loop in NextJS development environment #1436

Infinite redirect loop in NextJS development environment #1436

Comments

ghost commented Jun 29, 2023

Description

Package + Version

dimkl commented Jun 29, 2023

adarsh-gupta101 commented Jun 30, 2023

ghost commented Jun 30, 2023 • edited by ghost Loading

GuillaumeDesforges commented Jul 3, 2023

GuillaumeDesforges commented Jul 3, 2023 • edited Loading

nkeil commented Jul 10, 2023

ValkovMirec commented Jul 14, 2023 • edited Loading

aviroopjana commented Aug 5, 2023

catchshyam commented Aug 6, 2023

aviroopjana commented Aug 6, 2023

satishkumarsajjan commented Aug 7, 2023

satishkumarsajjan commented Aug 7, 2023

aviroopjana commented Aug 7, 2023

OkolieOKS234 commented Aug 7, 2023

royanger commented Aug 8, 2023

creative-tutorials commented Aug 12, 2023 • edited Loading

When I try clearing the cookies it works for me, but after saving a few changes to my code, it doesn't work anymore

creative-tutorials commented Aug 12, 2023

royanger commented Aug 13, 2023

creative-tutorials commented Aug 13, 2023

IAmTahazzot commented Aug 19, 2023 • edited Loading

creative-tutorials commented Aug 19, 2023 • edited Loading

emLuc86dev commented Aug 19, 2023

kachar commented Aug 20, 2023

creative-tutorials commented Aug 20, 2023

creative-tutorials commented Aug 20, 2023 • edited Loading

emLuc86dev commented Aug 20, 2023 via email

stx-chris commented Jan 15, 2024 • edited Loading

carlelgstroem commented Jan 22, 2024 • edited Loading

creative-tutorials commented Jan 26, 2024

eraoul commented Jan 29, 2024

creative-tutorials commented Jan 29, 2024

flean commented Jan 31, 2024

jameslporter commented Jan 31, 2024 via email

eraoul commented Jan 31, 2024

dnyn92 commented Feb 14, 2024 • edited Loading

alamenai commented Mar 9, 2024

alamenai commented Mar 9, 2024

dnyn92 commented Mar 14, 2024

creative-tutorials commented Mar 22, 2024 • edited Loading

yuvrajzingh commented Apr 14, 2024

nikos-pblworks commented Apr 23, 2024

alamenai commented Apr 30, 2024

hieutrluu commented May 7, 2024

jescalan commented May 7, 2024

Vipigal commented May 13, 2024

creative-tutorials commented May 13, 2024

i-am-chitti commented Aug 18, 2024

DevTaehong commented Oct 1, 2024

g-wozniak commented Dec 12, 2024

Vipigal commented Dec 13, 2024 via email

zohairhadi commented Feb 6, 2025 • edited Loading

jescalan commented Feb 7, 2025

ghost commented Jun 30, 2023 •

edited by ghost

Loading

GuillaumeDesforges commented Jul 3, 2023 •

edited

Loading

ValkovMirec commented Jul 14, 2023 •

edited

Loading

creative-tutorials commented Aug 12, 2023 •

edited

Loading

IAmTahazzot commented Aug 19, 2023 •

edited

Loading

creative-tutorials commented Aug 19, 2023 •

edited

Loading

creative-tutorials commented Aug 20, 2023 •

edited

Loading

stx-chris commented Jan 15, 2024 •

edited

Loading

carlelgstroem commented Jan 22, 2024 •

edited

Loading

dnyn92 commented Feb 14, 2024 •

edited

Loading

creative-tutorials commented Mar 22, 2024 •

edited

Loading

zohairhadi commented Feb 6, 2025 •

edited

Loading