Kibana server is not ready yet ~ missing authentication credentials for REST request

I installed Elasticsearch and Kibana 8.1.2 locally with standard configurations and without Docker on Windows 11. I just changed the passwords for all systems and bootstrap.
Elasticsearch is starting fine (using the bat-file). But when I start Kibana I see in the Browser (Chrome) for a second and than I get the message "Kibana server is not ready yet.".

Interesting at the cli is the line (full content below):

[ERROR][Elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. security_exception: [security_exception] Reason: missing authentication credentials for REST request [/_nodes?filter_path=nodes..version%2Cnodes..http.publish_address%2Cnodes.*.ip]

I tried to set the password at kibana.yml:

xpack.security.encryptionKey: "something_at_least_32_characters"

But the passwords I set before are shorter than 32 characters and to change the passwords a second time I get only this message:

The password for the 'elastic' user has already been changed on this cluster

The kibana.yml is empty (every thing is commented out).

How do I set the authentication credentials or how can I manage this problem?
Thanks, Frank

Here the cli log:

C:\kibana-8.1.2-windows-x86_64\kibana-8.1.2\bin>kibana.bat
[2022-04-12T16:16:56.129+02:00][INFO ][plugins-service] Plugin "metricsEntities" is disabled.
[2022-04-12T16:16:56.183+02:00][INFO ][http.server.Preboot] http server running at http://localhost:5601
[2022-04-12T16:16:56.219+02:00][INFO ][plugins-system.preboot] Setting up [1] plugins: [interactiveSetup]
[2022-04-12T16:16:56.222+02:00][INFO ][preboot] "interactiveSetup" plugin is holding setup: Validating Elasticsearch connection configuration…
[2022-04-12T16:16:56.248+02:00][INFO ][root] Holding setup until preboot stage is completed.
[2022-04-12T16:16:56.281+02:00][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.
[2022-04-12T16:16:56.409+02:00][INFO ][plugins-system.standard] Setting up [112] plugins: [translations,licensing,globalSearch,globalSearchProviders,features,mapsEms,licenseApiGuard,usageCollection,taskManager,telemetryCollectionManager,telemetryCollectionXpack,kibanaUsageCollection,sharedUX,share,embeddable,uiActionsEnhanced,screenshotMode,screenshotting,banners,telemetry,newsfeed,fieldFormats,expressions,dataViews,charts,esUiShared,bfetch,data,savedObjects,presentationUtil,expressionShape,expressionRevealImage,expressionRepeatImage,expressionMetric,expressionImage,customIntegrations,home,searchprofiler,painlessLab,grokdebugger,management,watcher,licenseManagement,advancedSettings,spaces,security,savedObjectsTagging,reporting,lists,fileUpload,ingestPipelines,encryptedSavedObjects,dataEnhanced,cloud,snapshotRestore,eventLog,actions,alerting,triggersActionsUi,transform,stackAlerts,ruleRegistry,savedObjectsManagement,console,controls,graph,fleet,indexManagement,remoteClusters,crossClusterReplication,indexLifecycleManagement,visualizations,canvas,visTypeXy,visTypeVislib,visTypeVega,visTypeTimeseries,rollup,visTypeTimelion,visTypeTagcloud,visTypeTable,visTypeMetric,visTypeHeatmap,visTypeMarkdown,dashboard,maps,dashboardEnhanced,expressionTagcloud,expressionPie,visTypePie,expressionMetricVis,expressionHeatmap,expressionGauge,dataViewFieldEditor,lens,cases,timelines,discover,osquery,observability,discoverEnhanced,dataVisualizer,ml,uptime,securitySolution,infra,upgradeAssistant,monitoring,logstash,enterpriseSearch,apm,dataViewManagement]
[2022-04-12T16:16:56.422+02:00][INFO ][plugins.taskManager] TaskManager is identified by the Kibana UUID: d0b08cb6-f946-4783-84ee-e2655b6e3299
[2022-04-12T16:16:56.532+02:00][WARN ][plugins.security.config] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command.
[2022-04-12T16:16:56.533+02:00][WARN ][plugins.security.config] Session cookies will be transmitted over insecure connections. This is not recommended.
[2022-04-12T16:16:56.547+02:00][WARN ][plugins.security.config] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command.
[2022-04-12T16:16:56.548+02:00][WARN ][plugins.security.config] Session cookies will be transmitted over insecure connections. This is not recommended.
[2022-04-12T16:16:56.570+02:00][WARN ][plugins.reporting.config] Generating a random key for xpack.reporting.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.reporting.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command.
[2022-04-12T16:16:56.580+02:00][WARN ][plugins.encryptedSavedObjects] Saved objects encryption key is not set. This will severely limit Kibana functionality. Please set xpack.encryptedSavedObjects.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command.
[2022-04-12T16:16:56.597+02:00][WARN ][plugins.actions] APIs are disabled because the Encrypted Saved Objects plugin is missing encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command.
[2022-04-12T16:16:56.613+02:00][WARN ][plugins.alerting] APIs are disabled because the Encrypted Saved Objects plugin is missing encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in the kibana.yml or use the bin/kibana-encryption-keys command.
[2022-04-12T16:16:56.636+02:00][INFO ][plugins.ruleRegistry] Installing common resources shared between all indices
[2022-04-12T16:16:57.095+02:00][INFO ][plugins.screenshotting.config] Chromium sandbox provides an additional layer of protection, and is supported for Win32 OS. Automatically enabling Chromium sandbox.
[2022-04-12T16:16:57.212+02:00][ERROR][Elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. security_exception: [security_exception] Reason: missing authentication credentials for REST request [/_nodes?filter_path=nodes..version%2Cnodes..http.publish_address%2Cnodes.*.ip]
[2022-04-12T16:16:58.024+02:00][INFO ][plugins.screenshotting.chromium] Browser executable: C:\kibana-8.1.2-windows-x86_64\kibana-8.1.2\x-pack\plugins\screenshotting\chromium\chrome-win\chrome.exe

Hi, frankmehlhop

Have you tried including the new Elasticsearch credentials in the kibana configuration file (kibana.yml)? This link shows some details on how to configure:

Thanks for your response!

Just now I got it working through installing elastic and kibana a second time.
What I made different compare to the first installation is

  • first I created a folder "ELK" and unzipped both in it.
  • than I used cmd without(!) admin rights.

So I got my credentials and token for kibana from elastic and kibana starts as it should, where I add the token and credentials.

Frankmehlhop,

When you installed Elasticsearch, it automatically creates the token and credentials for you. However, this token created during installation has a usage time of 30 min to use in kibana. If this time has expired you will have to generate a new token:

Install Elasticsearch from archive on Linux or MacOS | Elasticsearch Guide [8.1] | Elastic

When you install kibana it shows in your cmd the url with an id for access in your browser and in this url it will request the token that was generated in the Elasticsearch installation, as per the link:

Best regards

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