Listen EACCES 0.0.0.0:443

I followed Configuring Kibana on Docker | Kibana User Guide [6.1] | Elastic and I tried to adjust server.port to 443 (instead of 5601) and got following error:

kibana12-custom | {"type":"error","@timestamp":"2018-01-29T02:57:45Z","tags":["fatal"],"pid":1,"level":"fatal","error":{"message":"listen EACCES 0.0.0.0:443","name":"Error","stack":"Error: listen EACCES 0.0.0.0:443\n    at Object.exports._errnoException (util.js:1020:11)\n    at exports._exceptionWithHostPort (util.js:1043:20)\n    at Server._listen2 (net.js:1249:19)\n    at listen (net.js:1298:10)\n    at net.js:1408:9\n    at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)\n    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:81:10)","code":"EACCES"},"message":"listen EACCES 0.0.0.0:443"}
kibana12-custom | FATAL { Error: listen EACCES 0.0.0.0:443
kibana12-custom |     at Object.exports._errnoException (util.js:1020:11)
kibana12-custom |     at exports._exceptionWithHostPort (util.js:1043:20)
kibana12-custom |     at Server._listen2 (net.js:1249:19)
kibana12-custom |     at listen (net.js:1298:10)
kibana12-custom |     at net.js:1408:9
kibana12-custom |     at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)
kibana12-custom |     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:81:10)
kibana12-custom |   cause: 
kibana12-custom |    { Error: listen EACCES 0.0.0.0:443
kibana12-custom |        at Object.exports._errnoException (util.js:1020:11)
kibana12-custom |        at exports._exceptionWithHostPort (util.js:1043:20)
kibana12-custom |        at Server._listen2 (net.js:1249:19)
kibana12-custom |        at listen (net.js:1298:10)
kibana12-custom |        at net.js:1408:9
kibana12-custom |        at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)
kibana12-custom |        at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:81:10)
kibana12-custom |      code: 'EACCES',
kibana12-custom |      errno: 'EACCES',
kibana12-custom |      syscall: 'listen',
kibana12-custom |      address: '0.0.0.0',
kibana12-custom |      port: 443 },
kibana12-custom |   isOperational: true,
kibana12-custom |   code: 'EACCES',
kibana12-custom |   errno: 'EACCES',
kibana12-custom |   syscall: 'listen',
kibana12-custom |   address: '0.0.0.0',
kibana12-custom |   port: 443 }
kibana12-custom exited with code 1

... presumably due to fact that Kibana runs as non-root user (<1024 port limitation), if that's the case is there a way for me to start Kibana as root? security wise it should be OK since it'd run in it's own container anyways...

Please advise.

Hi,

We definitely run all procs as non root because of security reasons. So you can't run Kibana as root. May be you let docker handle the mapping? : docker run -p 443:5601 and that should take care of your problem?

Thanks @jarpy :slight_smile:

Cheers,
Bhavya

1 Like

That is actually an excellent idea! Why did I not think of that? :smiley:

Thank You so much!

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.