0

I am trying to get the DX CLI to successfully open on a sfdx force:auth:web:login command, but continue getting this error:

{ Error: listen EACCES: permission denied 127.0.0.1:1717
    at Server.setupListenHandle [as _listen2] (net.js:1253:19)
    at listenInCluster (net.js:1318:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1451:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)
  code: 'EACCES',
  errno: 'EACCES',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 1717 }
{ Error: listen EACCES: permission denied 127.0.0.1:1717
    at Server.setupListenHandle [as _listen2] (net.js:1253:19)
    at listenInCluster (net.js:1318:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1451:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)
  code: 'EACCES',
  errno: 'EACCES',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 1717 }
{ Error: listen EACCES: permission denied 127.0.0.1:1717
    at Server.setupListenHandle [as _listen2] (net.js:1253:19)
    at listenInCluster (net.js:1318:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1451:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)
  code: 'EACCES',
  errno: 'EACCES',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 1717 }
{ Error: listen EACCES: permission denied 127.0.0.1:1717
    at Server.setupListenHandle [as _listen2] (net.js:1253:19)
    at listenInCluster (net.js:1318:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1451:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)
  code: 'EACCES',
  errno: 'EACCES',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 1717 }

Other commands that don't involve an authentication callback seem to work.

This is from a personal machine, and I've tried: - reinstalling the DX CLI - default certificate path built into git, as well as an alternate path pointed at a certificate from a VS Code plugin called win-ca, same issue - toggling http.sslverify in my git config - changing the oauthLocalPort to items not in the Administered port range, which will get me to the login page, but the callback still uses 1717 and hits a localhost failure in the browser - turned off windows firewall completely (no other fw installed) - turned on the firewall and set allow rules for 1717 for both inbound and outbound, tcp and udp (reverted back to off afterwards) - used netstat to find any processes trying to use 1717, none found - when using a custom port, I get a LISTENING returned on a process ID for my custom port, doesn't help anything after I kill that process.

Any other suggestions as to why with a firewall completely off and no proxy involved, why this would still fail?

  • Windows: 10.0.18363.0
  • Node: 12.16.3 LTS
  • DX CLI: sfdx-cli/7.57.1-dbf54fc584

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.