Restarted dev server, 503 error: ENOENT: no such file or directory worker-56658-1.sock
I decided to restart my dev server, and now it's returning 503 errors of all of a sudden.
I get this showing up as the page title when I try access
I tried clearing out all the usual cache suspects.
Reinstalling everything
Rebuilding
And then firing up the server again
And the error is still happening.
This is the second time it's happened in one day. The first time, I found this github issue: https://github.com/nuxt/nuxt/issues/24170
One person suggested restarting the computer. I did that, but it didn't fix it.
Feels like erratic behavior so I'm not sure where to even look.
I just upgraded my node to v23.5.0 and nuxt to 3.15.0 to see if that would help with anything, but it didn't.
If it helps, my app is within a monorepo using a pnpm workspace. I am reference another package within the monorepo as a dependency for my nuxt app. I don't think its related as things were working for sometime...
I get this showing up as the page title when I try access
localhost:3000I tried clearing out all the usual cache suspects.
rm -rf .nuxt .output .node_modulesReinstalling everything
pnpm installRebuilding
pnpm run buildAnd then firing up the server again
pnpm devAnd the error is still happening.
This is the second time it's happened in one day. The first time, I found this github issue: https://github.com/nuxt/nuxt/issues/24170
One person suggested restarting the computer. I did that, but it didn't fix it.
Feels like erratic behavior so I'm not sure where to even look.
I just upgraded my node to v23.5.0 and nuxt to 3.15.0 to see if that would help with anything, but it didn't.
If it helps, my app is within a monorepo using a pnpm workspace. I am reference another package within the monorepo as a dependency for my nuxt app. I don't think its related as things were working for sometime...
GitHub
Environment Operating System: Windows 11 Node Version: v20.9.0 Nuxt Version: 3.6.1 Reproduction I'm not sure I can reproduce a 503 (Service Unavailable) error because it seems to be a server-si...
