Recently started getting "Error: aborted" randomly

[JamesSingleton]

So I randomly started getting the following error

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: aborted
    at connResetException (node:internal/errors:692:14)
    at abortIncoming (node:_http_server:602:17)
    at socketOnClose (node:_http_server:596:3)
    at Socket.emit (node:events:539:35)
    at Socket.emit (node:domain:475:12)
    at TCP.<anonymous> (node:net:709:12)
error - unhandledRejection: Error: aborted
    at connResetException (node:internal/errors:692:14)
    at abortIncoming (node:_http_server:602:17)
    at socketOnClose (node:_http_server:596:3)
    at Socket.emit (node:events:539:35)
    at Socket.emit (node:domain:475:12)
    at TCP.<anonymous> (node:net:709:12) {
  code: 'ECONNRESET'
}

It happens if I make my browser go from mobile view to desktop view using Chrome's DevTools and sometimes it will happen just refreshing the page. The only async code I have is either getStaticProps where I call sanityClient.fetch(someQuery) but that has never caused this before. I know this doesn't have any code to go off but that is because I have no idea where to even start.

[MehmetFaahem]

just update next version to canary-9
npm command: npm i [email protected]

[eric-burel]

Have this issue with 12.3.0 as well, seems fixed in 12.3.1

[meyer9]

Also was getting this in 12.3.0

[mahmoud-hadi]

I'm on 12.3.1 and still facing this error randomly.

[UnholyPhoenix]

I am also using 12.3.1 and this error happens a few times a day in our production. Should I downgrade to 12.2.4-canary.9?

[tlenex]

also facing this isssue on 12.3.3

[nvh3011]

also facing the issue on 13.4.1

[xiaolongkipsi]

face the same issue in latest version 13.5

[Neo-Ciber94]

Same in 13.5.4 using the app router, but only appears to happen when the request is cancelled but do not occur on GET requests

[Neo-Ciber94]

Still happening in 14.0.2

[golddydev]

I think this is due to the middleware.
I only have this issue, after I added middleware.
I fixed by removing middleware and adding custom logic to api.

[JamesSingleton]

I have no middleware in any of my projects though. Granted I haven't run into this issue in some time now/haven't looked for it.

[marcelino-borges]

Same here (NextJS 14.0.4)

[svey-xyz]

I am having the same issue with 14.1.0

[brycedbjork]

I am also experiencing this with 14.1.0

[jonnitg]

still happening in 14.2.3 ... it suddenly happened 1 min was ok and the next dev it was failing without any changes

[sokactomas]

I am having the same issue with 13.5.6

AbortError: The operation was aborted.
    at new DOMException (node:internal/per_context/domexception:53:5)
    at Object.destroy (node:internal/deps/undici/undici:10767:33)
    at httpFetch (node:internal/deps/undici/undici:10563:45)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async node:internal/deps/undici/undici:10342:20
    at async mainFetch (node:internal/deps/undici/undici:10332:20)
    ```
It happens only sometimes and only on production.

[faisal-saddique]

Following for updates

[Arhan13]

Facing the same issue on next 14.1.0

[work7z]

experiencing the same issue in next.js v14+

by the way, it's thrown in production env which is deployed as standalone mode

[Elham13]

Facing the same issue in next js 14.2.3

[bugswritter]

getting the same while using server actions

[redbmk]

Were you able to at least trace it down to the calling function? I'm seeing this in 14.2.3 as well and have no clue where it's coming from

[ignacionar]

Same for me in v14.2.4

[GainorB]

Facing the same issue with ^13.1.6

[Imunal]

Anyone find solution to this problem? Or wait is causing this error?

I'm running local server in Docker image (webServer in playwright config) when running E2E test in CI with Playwright, half of the time tests are failing because server is crashing with "Error: aborted", and needing to be reruned when failing and be prayed to not crash again :)

[ljhskyso]

any updates on this? not even sure what triggers the issue...

[magoz]

I'm also getting the error. I'm using middleware to setup CORS:

// https://nextjs.org/docs/app/building-your-application/routing/middleware#cors

const corsOptions = {
  'Access-Control-Allow-Methods': 'GET, POST, PUT, DELETE, OPTIONS',
  'Access-Control-Allow-Headers': 'Content-Type, Authorization'
}

const corsMiddleware = (request: NextRequest) => {
  const origin = '*'
  const isAllowedOrigin = true

  // Handle preflighted requests
  const isPreflight = request.method === 'OPTIONS'

  if (isPreflight) {
    const preflightHeaders = {
      ...(isAllowedOrigin && { 'Access-Control-Allow-Origin': origin }),
      ...corsOptions
    }
    return NextResponse.json({}, { headers: preflightHeaders })
  }

  // Handle simple requests
  const response = NextResponse.next()

  if (isAllowedOrigin) {
    response.headers.set('Access-Control-Allow-Origin', origin)
  }

  Object.entries(corsOptions).forEach(([key, value]) => {
    response.headers.set(key, value)
  })

  return response
}

[Imunal]

Yeah, anything in middleware will throw this error, but i still didn't find the workaround ;/ Maybe someone have better luck.

Any chance to take a look @leerob ?

[work7z]

frankly, my suggestion is not to use next.js

any leading-edge technology needs time to mitigate these issues

[teddarcuri]

This take isn't very constructive, but I actually agree with it.
I have invested my company in Next, but have some regrets. It's like every other day I have a new error cropping up - only to search for issues like this where there is no resolution, nor response.

[kenzaflow]

This take isn't very constructive, but I actually agree with it. I have invested my company in Next, but have some regrets. It's like every other day I have a new error cropping up - only to search for issues like this where there is no resolution, nor response.

This was working fine until Ctrl+S starts the infinite log POST/200 in 18ms, and when I reload the page with F5 it throws:

⨯ Error: aborted
    at abortIncoming (node:_http_server:797:17)
    at socketOnClose (node:_http_server:791:3)
    at Socket.emit (node:events:531:35)
    at TCP.<anonymous> (node:net:339:12)
digest: "3678400141"

I can't get rid of it, I've tried almost everything. It's full of bugs like this. I can't believe this is a "production framework", even recommended by React itself.

[Thomas-QCD]

⨯ Error: aborted
    at abortIncoming (node:_http_server:797:17)
    at socketOnClose (node:_http_server:791:3)
    at Socket.emit (node:events:531:35)
    at TCP.<anonymous> (node:net:339:12)
digest: "3678400141"

Currently having this issue on "^14.2.7".

[trungtin]

I have this issue, the cause is I'm streaming the response from server to client. After the streaming finish, there some tasks need to be done. So adding waitUntil from '@vercel/functions` to wait for these promises resolve this issue (this apply to local dev environment too)

[richg0ld]

15.0.3 version same issue

[22:52:50.823] ERROR (next.js): aborted
    err: {
      "type": "Error",
      "message": "aborted",
      "stack":
          Error: aborted
              at abortIncoming (node:_http_server:794:17)
              at socketOnClose (node:_http_server:788:3)
              at Socket.emit (node:events:530:35)
              at TCP.<anonymous> (node:net:337:12)
              at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
      "code": "ECONNRESET"
    }
[22:52:50.826] ERROR (next.js):  ⨯ uncaughtException:
    err: {
      "type": "Error",
      "message": "aborted",
      "stack":
          Error: aborted
              at abortIncoming (node:_http_server:794:17)
              at socketOnClose (node:_http_server:788:3)
              at Socket.emit (node:events:530:35)
              at TCP.<anonymous> (node:net:337:12)
              at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
      "code": "ECONNRESET"
    }
[22:52:50.826] ERROR (next.js):  ⨯ uncaughtException:
    err: {
      "type": "Error",
      "message": "aborted",
      "stack":
          Error: aborted
              at abortIncoming (node:_http_server:794:17)
              at socketOnClose (node:_http_server:788:3)
              at Socket.emit (node:events:530:35)
              at TCP.<anonymous> (node:net:337:12)
              at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
      "code": "ECONNRESET"
    }

[gary-jensen]

This was working fine until Ctrl+S

Error: aborted
at abortIncoming (node:_http_server:809:17)
at socketOnClose (node:_http_server:803:3)
at Socket.emit (node:events:536:35)
at TCP. (node:net:350:12)
at TCP.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'ECONNRESET'

Ctrl+S recreates this issue for me. No infinite loop here though.
It stems from the two occurences of fetch that I have in my custom hook.
If I either comment out the fetch statement or add an event listener for ctrl+s and preventDefault(), the issue goes away.

I'm not sure what's causing fetch to have this issue though.