ClerkJS: Token refresh failed. TypeError: Failed to fetch. Please try again.

[kachar]

• Review the documentation: https://clerk.com/docs
• Search for existing issues: https://github.com/clerkinc/javascript/issues
• Go through package changelog files.
• Provide the Frontend API key from your application dashboard.

NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_Y2xlcmsudGVhbS1ncHQuY29tJA

Package + Version

• @clerk/clerk-js
• @clerk/clerk-react
• @clerk/nextjs - 4.23.2
• @clerk/remix
• @clerk/types - 3.49.0
• @clerk/themes - 1.7.5
• @clerk/localizations
• @clerk/clerk-expo
• @clerk/backend - 0.27.0
• @clerk/clerk-sdk-node
• @clerk/shared
• @clerk/fastify
• @clerk/chrome-extension
• gatsby-plugin-clerk
• build/tooling/chore
• other:

Dependencies + versions

Provide a json with the dependencies used in your project (copy paste from yarn.lock / package-lock.json) or a github project / template that reproduces the issue.

Include the @clerk/ packages and their versions!*

Example:

{  
  "dependencies": {
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "next": "13.4.16",
    "axios": "^1.4.0",
    "@clerk/backend": "0.27.0",
    "@clerk/nextjs": "^4.23.2",
    "@clerk/themes": "1.7.5",
    "@clerk/types": "3.49.0",
    "@sentry/core": "^7.64.0",
    "@sentry/nextjs": "^7.64.0",
    "@sentry/node": "^7.64.0",
    "@sentry/profiling-node": "^1.1.2",
    "@sentry/utils": "^7.64.0"
  }
}

Browser/OS

If applicable e.g. Chrome {version}, Node {version} , Bun {version} , Cloudflare worker {version}

Description

We're experiencing a severe number of errors reported by Sentry regarding the Clerk user authentication. It happens ad-hoc and between releases.

Error
ClerkJS: Token refresh failed (error='ClerkJS: Network error at "https://clerk.our-domain.com/v1/client/sessions/sess_2TwhWEx3j9IvWXU0qOtEwutNLx2/tokens?_clerk_js_version=4.53.0" - TypeError: Failed to fetch. Please try again.')

Is there anything we can do to improve this process and reduce the errors for our customers?

[manutzsong]

I also have "Failed to fetch problem"

Solved it by downgrade to "@clerk/nextjs": "4.21.13",

[jescalan]

👋 Hey there @kachar! this is an issue that can happen with bots, but if it's happening with users it's a concern. If it's a bot, we should be able to block the bot as well (cc @anagstef)

Have you seen this error reported by real users or been able to reproduce it in any way? If not, you may be able to mute the error and move on.

@manutzsong - this seems like it is a separate issue, would you be willing to open a new issue to discuss this? Any more details you can provide, or a reproduction would be very useful here too.

[tmcw]

I can confirm that this is not a bot issue - we get it on a variety of browsers, and for logged-in users in Sentry:

[Andriy-Kulak]

@jescalan - we are getting a token refresh issue as well. it's a bad issue because the client essentially is locked out from the website and has to change browsers or clear cache. can you please look into this?

It's not acceptable for customers to be dealing with this & I see the same sentry errors as @tmcw . I unfortunately cannot recreate this issue locally.

[jescalan]

We'll discuss this one again, but it's quite difficult to look into without any way to reproduce it. Thank you both for the followup!

[dimkl]

Hello @Andriy-Kulak,
Are you getting a Token refresh failed ... TypeError: NetworkError ... or is it another type of token refresh failed issue?
There are multiple token refresh failed errors.

The above error is related to a NetworkError which may be caused by :

• CORS
• Networking issue

ref: JakeChampion/fetch#310

Is it possible to have any of the following information:

• https://replay.io/ recording
• a HAR of a failed request
• check the console if there is any CORS related error

cc: @tmcw , @kachar

[Andriy-Kulak]

@dimkl there were no cors errors This is the full error (abstracted our domain). What is HAR? does below help?

Error: ClerkJS: Token refresh failed (error='ClerkJS: Network error at "https://clerk.{ourdomain.com}/v1/client/sessions/sess_2UpTfftYexW5yvzcs9XhVau3uy8/tokens?_clerk_js_version=4.57.0" - TypeError: Failed to fetch. Please try again.')

This is not related to a firefox add on so JakeChampion/fetch#310 doesn't seem related

[dimkl]

@Andriy-Kulak the ref of JakeChampion/fetch#310 was added as a resource link for the causes I mentioned. I'm sorry for the misunderstanding, I didn't intend to indicate that the Firefox add-on was your issue.

Also, you can generate a HAR file following this: https://www.inflectra.com/Support/KnowledgeBase/KB254.aspx

Since you didn't find any CORS or Network related information on your Dev Tools a https://replay.io/ recording would be really helpful to pinpoint the issue.

[clerk-cookie]

Hello 👋

We currently close issues after 40 days of inactivity. It's been 30 days since the last update here. If we missed this issue, please reply here. Otherwise, we'll close this issue in 10 days.

As a friendly reminder: The best way to see an issue fixed is to open a pull request. If you're not sure how to do that, please check out our contributing guide.

Thanks for being a part of the Clerk community! 🙏

[emilpriver]

hello, I am experiencing this as well running on cloudflare pages togheter with remix.
I sometimes get a token and sometimes don't get a token.

There is no pattern to this