what this error
Unanswered
Toyger posted this in #help-forum
ToygerOP
TypeError: fetch failed
at Object.fetch (node:internal/deps/undici/undici:11576:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async invokeRequest (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\server-ipc\invoke-request.js:17:12)
at async invokeRender (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\router-server.js:254:29)
at async handleRequest (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\router-server.js:447:24)
at async requestHandler (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\router-server.js:464:13)
at async Server.<anonymous> (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\start-server.js:117:13) {
cause: Error: connect ECONNREFUSED ::1:51255
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
errno: -4078,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '::1',
port: 51255
}
}
at Object.fetch (node:internal/deps/undici/undici:11576:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async invokeRequest (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\server-ipc\invoke-request.js:17:12)
at async invokeRender (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\router-server.js:254:29)
at async handleRequest (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\router-server.js:447:24)
at async requestHandler (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\router-server.js:464:13)
at async Server.<anonymous> (C:\Users\bestw\Desktop\next\filesdownloader\node_modules\next\dist\server\lib\start-server.js:117:13) {
cause: Error: connect ECONNREFUSED ::1:51255
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
errno: -4078,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '::1',
port: 51255
}
}
30 Replies
Ragdoll
The endpoint is not responding , check if the api is correct
ToygerOP
how can i find this error
Ragdoll
what do you mean by
find this errorI think you should first understand how api / fetch work
@Ragdoll I think you should first understand how api / fetch work
ToygerOP
bro i dont use api
@joulev downgrade to 13.4.12
ToygerOP
okay i wait try again and If the page is refreshed with any modifications, a warning will appear and the project will also stop
@Toyger okay i wait try again and If the page is refreshed with any modifications, a warning will appear and the project will also stop
yes... this is a known nextjs 13.4.13+ bug
just downgrade to 13.4.12
@joulev downgrade to 13.4.12
ToygerOP
okay how can i install this
npm what
npm what
hmm
npm install next@13.4.12 try thisToygerOP
great
"next": "^13.4.12",
@Toyger "next": "^13.4.12",
hmm idt this works
pin it
remove the ^
to ensure it must be 13.4.12
changing to "next": "13.4.12" then run npm install
ToygerOP
Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/messages/fast-refresh-reload
Then the project stops
Then the project stops
yes that's a bug in 13.4.12 that has been fixed in latest
can't have both ways
i personally use 13.4.19 because the fetch error bug doesn't occur to me
ToygerOP
Okay, what can I do now? Is there a version that prevents this?
not that i know of
ToygerOP
Can I use the version that you are using, is there an error
@joulev i personally use 13.4.19 because the fetch error bug doesn't occur to me
i use 13.4.19, but as far as i know this fetch failed bug still occurs there
ig i'm just lucky
or the bug is platform-specific and not reproduced on macOS