503 Server Unavailable

Environment

• Operating System: Linux
• Node Version: v18.7.0
• Nuxt Version: 3.0.0-rc.12
• Nitro Version: 0.6.0
• Package Manager: npm@8.15.0
• Builder: vite
• User Config: srcDir, modules, compilerOptions, vue, vite, telemetry, algolia, head, auth, css, build, runtimeConfig
• Runtime Modules: genesis-design-system/nuxt, @nuxtjs/tailwindcss@5.3.5, @nuxtjs/algolia@1.1.4, @nuxtjs-alt/auth@2.0.20, @nuxtjs/device@3.0.0, unplugin-icons/nuxt, @pinia/nuxt@0.4.3, @nuxtjs/i18n@8.0.0-alpha.3
• Build Modules: -

Reproduction

we are crawling our website with screaming frog…

When we have about 1,500 urls tracked, the server crashes and starts throwing 503 errors.

And at that moment we try to make a request through the browser and it is already impossible.

You have to stop the server and start it again

Describe the bug

we are crawling our website with screaming frog…

When we have about 1,500 urls tracked, the server crashes and starts throwing 503 errors.

And at that moment we try to make a request through the browser and it is already impossible.

You have to stop the server and start it again

Additional context

No response

Logs

Error: socket hang up
    at connResetException (node:internal/errors:704:14)
    at Socket.socketOnEnd (node:_http_client:505:23)
    at Socket.emit (node:events:525:35)
    at Socket.emit (node:domain:489:12)
    at endReadableNT (node:internal/streams/readable:1359:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

[amihhs]

same issue

nitro\src\dev\server.ts

I found that it was caused by the return of false by existsSync (address.socketPath)

[amihhs]

hi @ae86jung , for me,I sent him return void instead of errrorHandle. So that api can work properly.(Everything is fine at the moment)