# Unable to login Kibana **URL:** \ **Category:** Search Guard\ **Created:** [July 4, 2018, 10:13am UTC](https://forum.search-guard.com/t/unable-to-login-kibana/994 "2018-07-04T10:13:51Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Ravi\_Sharma](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Ravi\_Sharma](https://forum.search-guard.com/u/Ravi_Sharma)\ **Post date:** [July 4, 2018, 10:13am UTC](https://forum.search-guard.com/t/unable-to-login-kibana/994/1 "2018-07-04T10:13:51Z")
When asking questions, please provide the following information: - Search Guard and Elasticsearch version 6.2.4-22.3 . and 6.2.4 - JVM version and operating system version 1.8 and Ubuntu 16.04 I’ve followed [https://sematext.com/blog/elasticsearch-kibana-security-search-guard/](https://sematext.com/blog/elasticsearch-kibana-security-search-guard/) this document to set up Search guard. [https://localhost:9200/\_searchguard/authinfo](https://localhost:9200/_searchguard/authinfo) {“user”: “User [name=admin, roles=[admin], requestedTenant=null]”,“user\_name”: “admin”,“user\_requested\_tenant”: null,“remote\_address”: “103.51.153.82:53266”,“backend\_roles”: [“admin”],“custom\_attribute\_names”: [“attr.internal.attribute1”,“attr.internal.attribute2”,“attr.internal.attribute3”],“sg\_roles”: [“sg\_all\_access”,“sg\_own\_index”],“sg\_tenants”: {“admin\_tenant”: true,“admin”: true},“principal”: null,“peer\_certificates”: “0”} Everything looks good from Elasticsearch side. I can access ES by https. In Kibana, I’ve configured below properties as mentioned in blog. elasticsearch.url: “[https://locahost:9200](https://locahost:9200)” elasticsearch.ssl.verificationMode: none But I’m not able to log in Kibana. It shows The Search Guard license information could not be loaded. Please contact your system administrator. Please help me here to fix it. My configuration is same as the mentioned blog. ---
**Author:** ![jkressin](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/jkressin/32/9_2.png) [@jkressin](https://forum.search-guard.com/u/jkressin)\ **Post date:** [July 4, 2018, 8:08pm UTC](https://forum.search-guard.com/t/unable-to-login-kibana/994/2 "2018-07-04T20:08:32Z")
This usually indicates that Kibana cannot reach Elasticsearch or there is some problem with the Kibana server user. You should see log statements regarding this in the Kibana logs as well. What do you see there? Also, please post the complete kibana.yml you are using. > **···** > > On Wednesday, July 4, 2018 at 12:13:51 PM UTC+2, Ravi Sharma wrote: > > > When asking questions, please provide the following information: > > > - Search Guard and Elasticsearch version > > > 6.2.4-22.3 . and 6.2.4 > > > > > > - JVM version and operating system version > > > 1.8 and Ubuntu 16.04 > > > > > > I’ve followed [https://sematext.com/blog/elasticsearch-kibana-security-search-guard/](https://sematext.com/blog/elasticsearch-kibana-security-search-guard/) this document to set up Search guard. > > > > > > [https://localhost:9200/\_searchguard/authinfo](https://localhost:9200/_searchguard/authinfo) > > > > > > {“user”: “User [name=admin, roles=[admin], requestedTenant=null]”,“user\_name”: “admin”,“user\_requested\_tenant”: null,“remote\_address”: “[103.51.153.82:53266](http://103.51.153.82:53266)”,“backend\_roles”: [“admin”],“custom\_attribute\_names”: [“attr.internal.attribute1”,“attr.internal.attribute2”,“attr.internal.attribute3”],“sg\_roles”: [“sg\_all\_access”,“sg\_own\_index”],“sg\_tenants”: {“admin\_tenant”: true,“admin”: true},“principal”: null,“peer\_certificates”: “0”} > > > > > > Everything looks good from Elasticsearch side. I can access ES by https. In Kibana, I’ve configured below properties as mentioned in blog. > > > elasticsearch.url: “[https://locahost:9200](https://locahost:9200)” > > > elasticsearch.ssl.verificationMode: none > > > > > > But I’m not able to log in Kibana. It shows The Search Guard license information could not be loaded. Please contact your system administrator. Please help me here to fix it. My configuration is same as the mentioned blog. > > > > > > > > > ---
**Author:** ![John\_K](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@John\_K](https://forum.search-guard.com/u/John_K)\ **Post date:** [September 12, 2018, 5:37pm UTC](https://forum.search-guard.com/t/unable-to-login-kibana/994/3 "2018-09-12T17:37:20Z")
If you re using secure HTTPS check the setting is ‘https’ elasticsearch.url: “[https://hostname.local:9200](https://hostname.local:9200)” > **···** > > On Wednesday, 4 July 2018 11:13:51 UTC+1, Ravi Sharma wrote: > > > When asking questions, please provide the following information: > > > - Search Guard and Elasticsearch version > > > 6.2.4-22.3 . and 6.2.4 > > > > > > - JVM version and operating system version > > > 1.8 and Ubuntu 16.04 > > > > > > I’ve followed [https://sematext.com/blog/elasticsearch-kibana-security-search-guard/](https://sematext.com/blog/elasticsearch-kibana-security-search-guard/) this document to set up Search guard. > > > > > > [https://localhost:9200/\_searchguard/authinfo](https://localhost:9200/_searchguard/authinfo) > > > > > > {“user”: “User [name=admin, roles=[admin], requestedTenant=null]”,“user\_name”: “admin”,“user\_requested\_tenant”: null,“remote\_address”: “[103.51.153.82:53266](http://103.51.153.82:53266)”,“backend\_roles”: [“admin”],“custom\_attribute\_names”: [“attr.internal.attribute1”,“attr.internal.attribute2”,“attr.internal.attribute3”],“sg\_roles”: [“sg\_all\_access”,“sg\_own\_index”],“sg\_tenants”: {“admin\_tenant”: true,“admin”: true},“principal”: null,“peer\_certificates”: “0”} > > > > > > Everything looks good from Elasticsearch side. I can access ES by https. In Kibana, I’ve configured below properties as mentioned in blog. > > > elasticsearch.url: “[https://locahost:9200](https://locahost:9200)” > > > elasticsearch.ssl.verificationMode: none > > > > > > But I’m not able to log in Kibana. It shows The Search Guard license information could not be loaded. Please contact your system administrator. Please help me here to fix it. My configuration is same as the mentioned blog. > > > > > > > > >