There's a new method for bootstrapping Kibana via an enrollment token ( https://www.elastic.co/guide/en/kibana/current/targz.html ). === If this is the first time you’re starting Kibana, this command generates a unique link in your terminal to enroll your Kibana instance with Elasticsearch. === But the interactiveSetup doesn't work on FreeBSD and the unique link doesn't appear. === # su -m www -c '/usr/local/www/kibana8/bin/kibana' [07:34:35.648][INFO ][node] Kibana process configured with roles: [background_tasks, ui] [07:34:50.448][INFO ][plugins-service] Plugin "cloudChat" is disabled. [07:34:50.449][INFO ][plugins-service] Plugin "cloudExperiments" is disabled. [07:34:50.449][INFO ][plugins-service] Plugin "cloudFullStory" is disabled. [07:34:50.449][INFO ][plugins-service] Plugin "cloudGainsight" is disabled. [07:34:50.458][INFO ][plugins-service] Plugin "profiling" is disabled. [07:34:50.543][INFO ][http.server.Preboot] http server running at http://localhost:5601 [07:34:50.597][INFO ][plugins-system.preboot] Setting up [1] plugins: [interactiveSetup] [07:34:50.600][INFO ][preboot] "interactiveSetup" plugin is holding setup: Validating Elasticsearch connection configuration… [07:34:50.649][INFO ][root] Holding setup until preboot stage is completed. [07:36:50.754][WARN ][config.deprecation] The default mechanism for Reporting privileges will work differently in future versions, which will affect the behavior of this cluster. Set "xpack.reporting.roles.enabled" to "false" to adopt the future behavior before upgrading. ... === But on Windows the unique link appears: === [07:13:59.866][INFO ][root] Holding setup until preboot stage is completed. i Kibana has not been configured. Go to http://localhost:5601/?code=809293 to get started. ... ===
(In reply to Boris Korzun from comment #0) I did an upgrade (in my WIP), switched downloads to Linux versions (instead of macOS) and: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [2023-07-30T08:39:48.695+00:00][INFO ][root] Holding setup until preboot stage is completed. i Kibana has not been configured. Go to http://0.0.0.0:5601/?code=815624 to get started. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I will update the instructions.
(In reply to Juraj Lutter from comment #1) Great news. Can you attach the patch for current (8.8.2) port for futher testing?
Do note that this port depends on www/node16 which expired on 2023-09-30
(In reply to Rene Ladan from comment #3) Ping?