EdgarNodeJS
edgar1579
TRIALOP
a year ago
Servidor escuchando en el puerto 8080
node:events:495
throw er; // Unhandled 'error' event
^Error: listen EADDRINUSE: address already in use :::8080
at Server.setupListenHandle [as _listen2] (node:net:1817:16)
at listenInCluster (node:net:1865:12)
at Server.listen (node:net:1953:7)
at Function.listen (/app/node_modules/express/lib/application.js:635:24)
at [file:///app/index.js:10:5](file:///app/index.js:10:5)
at [ModuleJob.run](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)Emitted 'error' event on Server instance at:
at emitErrorNT (node:net:1844:8)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '::',
port: 8080
}
Node.js v18.20.2
npm WARN config production Use --omit=dev instead.
edgarnodejs@1.0.0 start
node index.js
servidor corriendo en puerto 8080
Servidor escuchando en el puerto 8080
node:events:495
throw er; // Unhandled 'error' event
^Error: listen EADDRINUSE: address already in use :::8080
at Server.setupListenHandle [as _listen2] (node:net:1817:16)
at listenInCluster (node:net:1865:12)
at Server.listen (node:net:1953:7)
at Function.listen (/app/node_modules/express/lib/application.js:635:24)
at [file:///app/index.js:10:5](file:///app/index.js:10:5)
at [ModuleJob.run](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)Emitted 'error' event on Server instance at:
at emitErrorNT (node:net:1844:8)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '::',
port: 8080
}
Node.js v18.20.2
ⓘ Deployment information is only viewable by project members and Railway employees.
0 Replies