nuxt: 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)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 36 (12 by maintainers)
Rest assured, they are on my list. I’m on holiday at the moment, but first thing when I’m back 👍
same issue
nitro\src\dev\server.ts
I found that it was caused by the return of false by existsSync (address.socketPath)
I will try mount a reproduction project that throws the issue indicated in this post.
we are blocked the development of new website in out business with this issue.
Hi. You can keep track of this issue via https://github.com/unjs/nitro/issues/1454. It is something certainly to be resolved ASAP.
@danielroe Recently too much disappointed with these 2 issues in the nuxt 3.6.x releases…
The routes (Content )are not auto-generating for Nuxt static site, have to manually write in pre-renders… https://github.com/nuxt/nuxt/issues/13949#issuecomment-1637147930
The nitro issue: is causing me to write npm run dev every time,
I hope this gets resolved soon 😦 Nuxt is my fav framework
Any solution to this @danielroe , still coming in nuxt 3.6.3 - unable to send a reproduction , my muct time is going on just restarting the server to work
So what is the solution to this then?
hi @ae86jung , for me,I sent him return void instead of errrorHandle. So that api can work properly.(Everything is fine at the moment)
Yes, there was a nasty bug fixed in 3.2.39 that would exhibit this behaviour (crash subsequent requests if one error was emitted). Try upgrading your project-design-system vue version and see if that resolves the issue for you.