This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| elastic:run_kibana_on_standard_ports [2023/01/25 21:11] – created xmailadmin | elastic:run_kibana_on_standard_ports [2024/10/20 14:14] (current) – update with changes to 8.15 olaf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== Let Kibana (debian) 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. | ||
| + | |||
| + | NOTE: The following solution needs to be repeated when Kibana is updated by apt. | ||
| + | |||
| + | === 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 / | ||
| + | # Before version 8.15 | ||
| + | # setcap cap_net_bind_service=+epi / | ||
| + | # Since version 8.15 | ||
| + | setcap cap_net_bind_service=+epi / | ||
| + | </ | ||