


Code: Select all
ut-server@ut99:~/node-utstats-2-2.11.2$ npm run start
> start
> node server.js production
> Ready on http://localhost:6969
Failed to proxy http://127.0.0.1:43347/_next/image?url=%2Fimages%2Floading.png&w=32&q=75 Error: socket hang up
at connResetException (node:internal/errors:705:14)
at Socket.socketCloseListener (node:_http_client:467:25)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:301:12) {
code: 'ECONNRESET'
}
Error occurred handling /_next/image?url=%2Fimages%2Floading.png&w=32&q=75 Error: socket hang up
at connResetException (node:internal/errors:705:14)
at Socket.socketCloseListener (node:_http_client:467:25)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:301:12) {
code: 'ECONNRESET'
}
Failed to proxy http://127.0.0.1:43347/api/home Error: socket hang up
at connResetException (node:internal/errors:705:14)
at Socket.socketCloseListener (node:_http_client:467:25)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:301:12) {
code: 'ECONNRESET'
}
Error occurred handling /api/home Error: socket hang up
at connResetException (node:internal/errors:705:14)
at Socket.socketCloseListener (node:_http_client:467:25)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:301:12) {
code: 'ECONNRESET'
}
Failed to proxy http://127.0.0.1:43347/api/home Error: socket hang up
at connResetException (node:internal/errors:705:14)
at Socket.socketCloseListener (node:_http_client:467:25)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:301:12) {
code: 'ECONNRESET'
}
Error occurred handling /api/home Error: socket hang up
at connResetException (node:internal/errors:705:14)
at Socket.socketCloseListener (node:_http_client:467:25)
at Socket.emit (node:events:525:35)
at TCP.<anonymous> (node:net:301:12) {
code: 'ECONNRESET'
}
Hello, after many tests, I have found the problem,UT Sniper (SJA94) wrote: ↑Mon Aug 14, 2023 12:44 pm Did you make sure to run <b>npm run build</b> before running <b>npm run start</b>? It looks like something to do with Next.js's Image, I did a quick search but couldn't find anything useful to see what the problem is. It's not port 43347 being blocked by something?