ERROR [nitro] [uncaughtException] listen EADDRINUSE: address already in use /tmp/nitro/worker-29-1.sock #127388
Unanswered
techglide123
asked this question in
Programming Help
Replies: 2 comments
-
Thanks for posting in the GitHub Community, @techglide123 ! We’ve moved your post to our Programming Help 🧑💻 category, which is more appropriate for this type of discussion. Please review our guidelines about the Programming Help category for more information. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @techglide123, It's been a couple days since you posted so you've likely solved this by now! It seems like you had another terminal open with the program running so the local address was already in use. Was that the issue? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Bug
Body
ERROR [nitro] [uncaughtException] listen EADDRINUSE: address already in use /tmp/nitro/worker-29-1.sock
at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
at __node_internal_uvExceptionWithHostPort (node:internal/errors:593:12)
at Server.setupListenHandle [as _listen2] (node:net:1800:21)
at listenInCluster (node:net:1865:12)
at Server.listen (node:net:1964:5)
at (node_modules/nitropack/dist/runtime/entries/nitro-dev.mjs:39:25)
at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:337:24)
at async loadESM (node:internal/process/esm_loader:34:7)
at async handleMainPromise (node:internal/modules/run_main:106:12)
Beta Was this translation helpful? Give feedback.
All reactions