# X-pack 5.1.1 error in kibana
**URL:** https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397
**Category:** Kibana
**Created:** [January 3, 2017, 7:03am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397 "2017-01-03T07:03:54Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@Lucifer\_hbp](https://discuss.elastic.co/u/Lucifer_hbp)
#### Post date: [January 3, 2017, 7:03am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/1 "2017-01-03T07:03:54Z")
Hi,
## I have elasticsearch 5.1.1 & kibana 5.1.1, I installed x-pack 5.1.1 in both, but after restarting kibana i am getting following message in kibana:
[06:52:32.441] [info][status][ui settings] Status changed from uninitialized to green - Ready
[06:53:01.768] [warning][license][xpack] License information could not be obtained from Elasticsearch. [illegal\_argument\_exception
] No endpoint or operation is available at [\_xpack] :: {"path":"/\_xpack","statusCode":400,"response":"{"error":{"root\_cause":[{"type
":"illegal\_argument\_exception","reason":"No endpoint or operation is available at [\_xpack]"}],"type":"illegal\_argument\_exception
","reason":"No endpoint or operation is available at [\_xpack]"},"status":400}"}
Unhandled rejection [illegal\_argument\_exception] No endpoint or operation is available at [\_xpack] :: {"path":"/\_xpack","statusCode":400,"
response":"{"error":{"root\_cause":[{"type":"illegal\_argument\_exception","reason":"No endpoint or operation is available at [\_xp
ack]"}],"type":"illegal\_argument\_exception","reason":"No endpoint or operation is available at [\_xpack]"},"status":400}"}
at respond (D:\Elastic stack\kibana-5.1.1-windows-x86\node\_modules\elasticsearch\src\lib\transport.js:289:15)
at checkRespForFailure (D:\Elastic stack\kibana-5.1.1-windows-x86\node\_modules\elasticsearch\src\lib\transport.j
s:248:7)
at HttpConnector. (D:\Elastic stack\kibana-5.1.1-windows-x86\node\_modules\elasticsearch\src\lib\conne
ctors\http.js:164:7)
at IncomingMessage.wrapper (D:\Elastic stack\kibana-5.1.1-windows-x86\node\_modules\elasticsearch\node\_modules\lo
dash\lodash.js:4994:19)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (\_stream\_readable.js:974:12)
at \_combinedTickCallback (internal/process/next\_tick.js:74:11)
at process.\_tickDomainCallback (internal/process/next\_tick.js:122:9)
And in browser i am unable to access localhost:5601
Any help please!!!! ,
Thanks,
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [January 3, 2017, 7:25am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/2 "2017-01-03T07:25:07Z")
Can you access `localhost:9200`?
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [January 3, 2017, 7:59am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/3 "2017-01-03T07:59:35Z")
This looks as if the `x-pack` plugin on the elasticsearch side was not installed successfully, can you rerun `bin/elasticsearch-plugin install x-pack` - make sure you finish the installation by manually agreeing on the ask for security permissions.
---
### Author:  [@Lucifer\_hbp](https://discuss.elastic.co/u/Lucifer_hbp)
#### Post date: [January 3, 2017, 8:21am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/4 "2017-01-03T08:21:30Z")
Thanks for the reply,
Yes localhost:9200 is accessible & output is:
{
"name" : "JMnD7eU",
"cluster\_name" : "App-Cluster",
"cluster\_uuid" : "pmE-CY9l6NuVK0TCpvIMKg",
"version" : {
"number" : "5.1.1",
"build\_hash" : "4455e21",
"build\_date" : "2016-12-06T12:36:15.409Z",
"build\_snapshot" : false,
"lucene\_version" : "6.3.0"
},
"tagline" : "You Know, for Search"
}
---
### Author:  [@Lucifer\_hbp](https://discuss.elastic.co/u/Lucifer_hbp)
#### Post date: [January 3, 2017, 8:22am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/5 "2017-01-03T08:22:52Z")
Yes , i installed xpack in elasticsearch 5.1.1 by manually agreeing security persmission & finally it showed that successfully installed x-pack!!!!!
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [January 3, 2017, 8:37am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/6 "2017-01-03T08:37:46Z")
Hey,
great to see it working. An easy to check for installed plugins would be one of
```auto
curl 'localhost:9200/_nodes/plugins?filter_path=**.plugins.name&pretty'
curl 'localhost:9200/_cat/plugins'
```
If you dont want to agree manually on the permissions, there is also a batch mode available when installing the plugin using `-b`
--Alex
---
### Author:  [@Lucifer\_hbp](https://discuss.elastic.co/u/Lucifer_hbp)
#### Post date: [January 3, 2017, 8:49am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/7 "2017-01-03T08:49:48Z")
Thanks again, its working i have to created user in elasticsearch & same added in kibana config & its working 🙂
---
### Author:  [@Ultralite](https://discuss.elastic.co/u/Ultralite)
#### Post date: [January 6, 2017, 11:16am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/8 "2017-01-06T11:16:21Z")
Hello,
same issue here.
What do you mean by create user for elasticsearch and kibana?
I've installed ELK with the yum install command.
---
### Author:  [@Lucifer\_hbp](https://discuss.elastic.co/u/Lucifer_hbp)
#### Post date: [January 10, 2017, 10:45am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/9 "2017-01-10T10:45:59Z")
After installing xpack ,shields gets in place so in Elasticsearch we must create a user with admin role and same credentials we must add in kibana.yml.
It worked for me, hope it 'll work!!!!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 7, 2017, 10:46am UTC](https://discuss.elastic.co/t/x-pack-5-1-1-error-in-kibana/70397/10 "2017-02-07T10:46:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.