# Access Kibana without setting a PORT number

**URL:** <https://discuss.elastic.co/t/access-kibana-without-setting-a-port-number/166201>\
**Category:** Kibana\
**Created:** [January 29, 2019, 3:39pm UTC](https://discuss.elastic.co/t/access-kibana-without-setting-a-port-number/166201 "2019-01-29T15:39:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Omar\_1CPI2011\_BRAHIM](https://avatars.discourse-cdn.com/v4/letter/o/9de0a6/32.png) [@Omar\_1CPI2011\_BRAHIM](https://discuss.elastic.co/u/Omar_1CPI2011_BRAHIM)\
**Post date:** [January 29, 2019, 3:39pm UTC](https://discuss.elastic.co/t/access-kibana-without-setting-a-port-number/166201/1 "2019-01-29T15:39:57Z")

</div>

Hello,

I'm running Kibana with its default configuration (Server\_Ip = A.B.C.D and Server\_Port=5601).

I would like to access it with my DNS sub-domain [kibana.mydomain.com](http://kibana.mydomain.com)  
But unfortunately, is my DNS, there is no way to setup my sub-domain [kibana.mydomain.com](http://kibana.mydomain.com) to this kind of link IP\_address:Port\_number, I can just redirect a sub-domain to an IP\_address without putting the Port\_number.

So, is there any solution on my server side (where I have installed kibana) to setup this kind of configuration and be able to access Kibana by using my sub-domain ?

Regards,

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [January 29, 2019, 5:41pm UTC](https://discuss.elastic.co/t/access-kibana-without-setting-a-port-number/166201/2 "2019-01-29T17:41:17Z")

</div>

Hey @Omar_1CPI2011_BRAHIM, you can set `server.port` in your [kibana.yml](https://www.elastic.co/guide/en/kibana/current/settings.html) to 80/443, which are the defaults for http/https, and then the user won't need to type in the port number explicitly.

---

<div class="post-metadata">

**Author:** ![Omar\_1CPI2011\_BRAHIM](https://avatars.discourse-cdn.com/v4/letter/o/9de0a6/32.png) [@Omar\_1CPI2011\_BRAHIM](https://discuss.elastic.co/u/Omar_1CPI2011_BRAHIM)\
**Post date:** [January 30, 2019, 8:39am UTC](https://discuss.elastic.co/t/access-kibana-without-setting-a-port-number/166201/3 "2019-01-30T08:39:40Z")

</div>

Thank you @Brandon_Kobel, I did that configuration (server.port: 443) but I got this error

```
log [08:34:10.993] [info][status][plugin:reporting@6.3.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch
 error [08:34:11.030] [fatal] Error: listen EACCES 0.0.0.0:443
    at Object._errnoException (util.js:992:11)
    at _exceptionWithHostPort (util.js:1014:20)
    at Server.setupListenHandle [as _listen2] (net.js:1338:19)
    at listenInCluster (net.js:1396:12)
    at doListen (net.js:1505:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
FATAL { Error: listen EACCES 0.0.0.0:443
    at Object._errnoException (util.js:992:11)
    at _exceptionWithHostPort (util.js:1014:20)
    at Server.setupListenHandle [as _listen2] (net.js:1338:19)
    at listenInCluster (net.js:1396:12)
    at doListen (net.js:1505:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
  cause: 
   { Error: listen EACCES 0.0.0.0:443
    at Object._errnoException (util.js:992:11)
    at _exceptionWithHostPort (util.js:1014:20)
    at Server.setupListenHandle [as _listen2] (net.js:1338:19)
    at listenInCluster (net.js:1396:12)
    at doListen (net.js:1505:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
     code: 'EACCES',
     errno: 'EACCES',
     syscall: 'listen',
     address: '0.0.0.0',
     port: 443 },
  isOperational: true,
  code: 'EACCES',
  errno: 'EACCES',
  syscall: 'listen',
  address: '0.0.0.0',
  port: 443 } 

```

And I got the same error when setting the server.port to 80

---

<div class="post-metadata">

**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\
**Post date:** [January 30, 2019, 2:30pm UTC](https://discuss.elastic.co/t/access-kibana-without-setting-a-port-number/166201/4 "2019-01-30T14:30:57Z")

</div>

@Omar_1CPI2011_BRAHIM, ports 0-1024 can only be bound to be "root", which is why you're getting this error. Depending on your OS, there might be other ways to get around this restriction besides running Kibana as root.

---

<div class="post-metadata">

**Author:** ![Omar\_1CPI2011\_BRAHIM](https://avatars.discourse-cdn.com/v4/letter/o/9de0a6/32.png) [@Omar\_1CPI2011\_BRAHIM](https://discuss.elastic.co/u/Omar_1CPI2011_BRAHIM)\
**Post date:** [January 31, 2019, 1:18pm UTC](https://discuss.elastic.co/t/access-kibana-without-setting-a-port-number/166201/5 "2019-01-31T13:18:46Z")

</div>

Thank you @Brandon_Kobel your answer is very helpful 🙂

---

<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 28, 2019, 1:18pm UTC](https://discuss.elastic.co/t/access-kibana-without-setting-a-port-number/166201/6 "2019-02-28T13:18:46Z")

</div>

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