User Tools
run_kibana_on_standard_ports
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| run_kibana_on_standard_ports [2023/01/21 13:30] – ↷ Page name changed from map_standard_ports_80_or_443_to_access_kibana to run_kibana_on_standard_ports xmailadmin | run_kibana_on_standard_ports [2023/01/25 21:10] (current) – removed xmailadmin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Let Kibana run on standard ports (HTTP :80 or HTTPS :443) ===== | ||
| - | |||
| - | Without changing the default configuration, | ||
| - | In kibana.yml the line '' | ||
| - | |||
| - | When the standard port for HTTP (:443) is configured for Kibana in kibana.yml\\ | ||
| - | '' | ||
| - | Kibana fails to start the next time with:\\ | ||
| - | '' | ||
| - | |||
| - | When running this as '' | ||
| - | The problem is that Kibana is lacking the permissions to bind to the standard ports by default. | ||
| - | |||
| - | === Solution === | ||
| - | As root or with sudo run: | ||
| - | <code bash> | ||
| - | setcap cap_net_bind_service=+epi / | ||
| - | setcap cap_net_bind_service=+epi / | ||
| - | setcap cap_net_bind_service=+epi / | ||
| - | setcap cap_net_bind_service=+epi / | ||
| - | |||
| - | </ | ||
| - | |||
| - | |||
| - | |||
run_kibana_on_standard_ports.1674307827.txt.gz · Last modified: by xmailadmin