The localhost gets disconnected while rendering the NextJS 13 application
Answered
Santhosh Prabhakaran posted this in #help-forum
In my NextJS 13 application, The localhost getting disconnected when the application gets re-render while developing. I'm also getting this error in my terminal
Any help on this would be appreciated.
TypeError: fetch failed
at Object.processResponse (node:internal/deps/undici/undici:6406:34)
at node:internal/deps/undici/undici:6727:42
at node:internal/process/task_queues:140:7
at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
cause: Error: connect ECONNREFUSED 127.0.0.1:33777
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 33777
}
}Any help on this would be appreciated.
Answered by joulev
seems like a nextjs bug, try downgrading to 13.4.12 https://nextjs-forum.com/post/1141790913052553216
8 Replies
what is port 33777?
@Santhosh Prabhakaran In my NextJS 13 application, The localhost getting disconnected when the application gets re-render while developing. I'm also getting this error in my terminal
`TypeError: fetch failed
at Object.processResponse (node:internal/deps/undici/undici:6406:34)
at node:internal/deps/undici/undici:6727:42
at node:internal/process/task_queues:140:7
at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
cause: Error: connect ECONNREFUSED 127.0.0.1:33777
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 33777
}
}`
Any help on this would be appreciated.
seems like a nextjs bug, try downgrading to 13.4.12 https://nextjs-forum.com/post/1141790913052553216
Answer
relevant issue: https://github.com/vercel/next.js/issues/53171
@joulev seems like a nextjs bug, try downgrading to 13.4.12 https://discord.com/channels/752553802359505017/1141790913052553216
Am I able to downgrade while working in latest ?
Does it affect any other things ?
European sprat
yeah it might if you are using some feature that doesn't exist in the downgraded version
but you can just try and go back if it breaks
@joulev seems like a nextjs bug, try downgrading to 13.4.12 https://discord.com/channels/752553802359505017/1141790913052553216
Yeah, Downgrading the next's version solved the issue.