This was raised here in the past, yet I couldn't find the answer for my use case:
I installed Logstash (5.6.0), ElasticSearch (5.6.0) and Kibana (5.6.0) in the same machine. I was able to access Kibana and play a little with elasticsearch.
After I installed x-pack (5.6.0), I recieved the following message when I'm trying to enter Kibana's portal:
"_Login is currently disabled because the license could not be determined. Please check that Elasticsearch has the X-Pack plugin installed and is reachable, then refresh this page."
I read here that I need to update the expired license (which was expired after 2 days - odd), but I can't update the new downloaded license, because I can't access Kibana.
Please help.
Please bare in mind that this is my first experience with ES
I followed the instractions and received the follow response:
PS C:\Users\Administrator> gc .\yossi-carmon-05378c9c-9e7a-4778-92e8-dc42ef0bc0d1-v5.json | Invoke-WebRequest -uri http
://localhost:9200/_xpack/license -Credential Administrator -Method Put
Invoke-WebRequest : Unable to connect to the remote server
At line:1 char:67
This is something I just recently started experiencing as well after recent updates to my cluster. My elasticsearch logs do show the license as valid and I've tried refreshing it. And Kibana continuously says the license could not be determined.
Could this be an issue with the x-pack plugin for Kibana? Because in the past I have manually upgraded the x-pack plugin like I usually do after an update/upgrade and that cluster has always come back fine now for except for this time.
Any input and feedback on this would be greatly appreciated.
I'm currently on 5.6.0 and all I have been doing since the update is restarting both elasticsearch and kibana on my kibana hosts, reinstalling plugins, refreshing license and tweaking kibana.yaml with no luck.
I see there's now a 5.6.1-1 available on my local repositories, would this address this bug you mention?
I now created a clean VM machine with windows 2016 server and clean installation of ES 5.6.1, Kibana 5.6.1, Logstash and X-Pack.
I finished to install ES, and now I'm finishing the installation for Kibana.
I will run it before I will install X-Pack, so you can compare both logs.
Give me 10 min to send it to you
This is the log after installing version 5.6.1 for ES and Kibana. I CAN access Kibana
C:\kibana-5.6.1-windows-x86\bin>kibana
log [04:21:11.552] [info][status][plugin:kibana@5.6.1] Status changed from uninitialized to green - Ready
log [04:21:11.631] [info][status][plugin:elasticsearch@5.6.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [04:21:11.646] [info][status][plugin:console@5.6.1] Status changed from uninitialized to green - Ready
log [04:21:11.662] [info][status][plugin:metrics@5.6.1] Status changed from uninitialized to green - Ready
log [04:21:11.849] [info][status][plugin:timelion@5.6.1] Status changed from uninitialized to green - Ready
log [04:21:11.849] [info][listening] Server running at http://localhost:5601
log [04:21:11.849] [info][status][ui settings] Status changed from uninitialized to yellow - Elasticsearch plugin is yellow
log [04:21:16.927] [info][status][plugin:elasticsearch@5.6.1] Status changed from yellow to yellow - No existing Kibana index found
log [04:21:18.256] [info][status][plugin:elasticsearch@5.6.1] Status changed from yellow to green - Kibana index ready
log [04:21:18.256] [info][status][ui settings] Status changed from yellow to green - Ready
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.