Access Kibana without setting a PORT number

Elastic Stack Kibana
1

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
But unfortunately, is my DNS, there is no way to setup my sub-domain 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,

2

Hey @Omar_1CPI2011_BRAHIM, you can set server.port in your kibana.yml to 80/443, which are the defaults for http/https, and then the user won't need to type in the port number explicitly.

3

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

4

@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.

1 Like
5

Thank you @Brandon_Kobel your answer is very helpful :slight_smile:

6

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