Error: listen EACCES: permission denied 0.0.0.0:3000

OS info

  • Operating System : Windows 10.0.18362
  • Wappler Version : 3.5.4

Problem description

Since updating Wappler I can no longer get the server to run. I haven’t made any changes, so this was working fine before the update.

Error: Error: listen EACCES: permission denied 0.0.0.0:3000

events.js:288
      throw er; // Unhandled 'error' event
      ^

Error: listen EACCES: permission denied 0.0.0.0:3000
    at Server.setupListenHandle [as _listen2] (net.js:1292:21)
    at listenInCluster (net.js:1357:12)
    at Server.listen (net.js:1445:7)
    at Object.start (C:\Data\Wappler\Projects\Inossis\CDS\lib\server.js:63:16)
    at Object.<anonymous> (C:\Data\Wappler\Projects\Inossis\CDS\index.js:3:8)
    at Module._compile (internal/modules/cjs/loader.js:1158:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
    at Module.load (internal/modules/cjs/loader.js:1002:32)
    at Function.Module._load (internal/modules/cjs/loader.js:901:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1336:8)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'EACCES',
  errno: 'EACCES',
  syscall: 'listen',
  address: '0.0.0.0',
  port: 3000
}

And no, the port is not opened elsewhere, I checked, and I do not have Windows firewall enabled on my private network connection. I also tried running Wappler as admin. As I said, this was working before the update.

Update: Seems for some reason all ports 3000-3040 are no longer accessible. I have no idea why this is now, but setting a port above 3040 seems to work. Will have to figure out why those ports are inaccessible, since the ports are not in use (at least netstat -ab shows no process using them).

Maybe a try restarting your pc? Seems somehow the parts are blocked/in use.

I have, but it seems related to installing WSL2 recently (and upgrading Windows 10 just prior). It could be the WSL2 VM is locking those ports for possible use, or they are required behind the scenes in some special way.