Error: bind EACCES null:1337

[whwnow]

Describe the bug
After executing the command npm run develop， an error is displayed

[2020-01-22T15:25:07.637Z] error Error: bind EACCES null:1337
    at listenOnMasterHandle (net.js:1326:16)
    at rr (internal/cluster/child.js:126:12)
    at Worker.send (internal/cluster/child.js:93:7)
    at process.onInternalMessage (internal/cluster/utils.js:43:8)
    at process.emit (events.js:198:15)
    at emit (internal/child_process.js:848:12)
    at processTicksAndRejections (internal/process/task_queues.js:81:17)

And I have checked that port 1337 is not occupied

Steps to reproduce the behavior

1. npx create-strapi-app my-project --quickstart
2. npm run develop

Expected behavior
A clear and concise description of what you expected to happen.

System

• Node.js version: 12.13.0
• NPM version: 6.12.0
• Strapi version: 3.0.0-beta.18.5
• Database: SqlLite
• Operating system: Windows 10

[lauriejim]

Hello! Do you have a port restriction in your machine?

[whwnow]

I have reset my firewall and the problem persists. Why the error message is null:1337, not localhost:1337

[derrickmehaffy]

@whwnow can you provide your config/environments/*/server.json please?

My guess is you are trying to change the host value with something that isn't supported.

[whwnow]

config/environments/development/server.json

{
  "host": "localhost",
  "port": 1337,
  "proxy": {
    "enabled": false
  },
  "cron": {
    "enabled": false
  },
  "admin": {
    "autoOpen": false
  }
}

This is the config. I have not modified the default configuration

[derrickmehaffy]

🤔 This is quite odd I am not able to reproduce this.

[panoti]

I have the same problem on Windows 10

[2020-02-07T04:37:10.097Z] error Error: bind EACCES null:1337
    at listenOnMasterHandle (net.js:1365:16)
    at rr (internal/cluster/child.js:129:12)
    at Worker.<anonymous> (internal/cluster/child.js:96:7)
    at process.onInternalMessage (internal/cluster/utils.js:43:8)
    at process.emit (events.js:214:15)
    at emit (internal/child_process.js:876:12)
    at processTicksAndRejections (internal/process/task_queues.js:81:21)

I workaround by changing port 1337 to 8082. then it works!

[lauriejim]

Did you have another app that uses this port?

[panoti]

@lauriejim I check my open port on my window by command netstat -an | find /i "listening"

Results:

  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1024           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2063           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2179           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5040           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:7680           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49664          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49665          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49666          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49667          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49668          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49669          0.0.0.0:0              LISTENING
  TCP    10.0.75.1:139          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1845         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1851         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:2111         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:2375         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:7173         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:15292        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:15393        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:18171        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:23401        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:45623        0.0.0.0:0              LISTENING
  TCP    192.168.19.113:139     0.0.0.0:0              LISTENING
  TCP    192.168.31.133:139     0.0.0.0:0              LISTENING
  TCP    [::]:135               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:1024              [::]:0                 LISTENING
  TCP    [::]:2179              [::]:0                 LISTENING
  TCP    [::]:7680              [::]:0                 LISTENING
  TCP    [::]:49664             [::]:0                 LISTENING
  TCP    [::]:49665             [::]:0                 LISTENING
  TCP    [::]:49666             [::]:0                 LISTENING
  TCP    [::]:49667             [::]:0                 LISTENING
  TCP    [::]:49668             [::]:0                 LISTENING
  TCP    [::]:49669             [::]:0                 LISTENING

There is no any apps opening 1337 port. I think Windows 10 restrict 1337 port.

[lorduakiti]

I have the same problem for port 3001 using the custom configuration.

server.json

{
  "host": "localhost",
  "port": 3001,
  "proxy": {
    "enabled": false
  },
  "cron": {
    "enabled": false
  },
  "admin": {
    "autoOpen": true
  }
}

[derrickmehaffy]

If you guys are on linux/mac please run a netstat -plnt in the terminal and provide the response

[derrickmehaffy]

As I have seen no updates to this and we are currently unable to reproduce I'm going to mark this as closed, should you still have issues please provide any guidance on reproducing this issue.

[w3bdesign]

I had this problem as well today.

I had to change the port number in config\environments\development\server.json to get it to work.

[Huskydog9988]

same as w3bdesign