# Listen EACCES 0.0.0.0:443

**URL:** <https://discuss.elastic.co/t/listen-eacces-0-0-0-0-443/117393>\
**Category:** Kibana\
**Created:** [January 29, 2018, 3:54am UTC](https://discuss.elastic.co/t/listen-eacces-0-0-0-0-443/117393 "2018-01-29T03:54:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [January 29, 2018, 3:54am UTC](https://discuss.elastic.co/t/listen-eacces-0-0-0-0-443/117393/1 "2018-01-29T03:54:25Z")

</div>

I followed [Configuring Kibana on Docker | Kibana User Guide [6.1] | Elastic](https://www.elastic.co/guide/en/kibana/current/_configuring_kibana_on_docker.html) 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.

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [January 29, 2018, 5:34am UTC](https://discuss.elastic.co/t/listen-eacces-0-0-0-0-443/117393/2 "2018-01-29T05:34:08Z")

</div>

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 🙂

Cheers,  
Bhavya

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [January 29, 2018, 3:46pm UTC](https://discuss.elastic.co/t/listen-eacces-0-0-0-0-443/117393/3 "2018-01-29T15:46:51Z")

</div>

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

Thank You so much!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 26, 2018, 3:46pm UTC](https://discuss.elastic.co/t/listen-eacces-0-0-0-0-443/117393/4 "2018-02-26T15:46:52Z")

</div>

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