# Could not login: Login is currently disabled. Administrators should consult the Kibana logs for more details **URL:** \ **Category:** Kibana\ **Created:** [August 1, 2018, 7:37am UTC](https://discuss.elastic.co/t/could-not-login-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/142488 "2018-08-01T07:37:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Shree](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@Shree](https://discuss.elastic.co/u/Shree)\ **Post date:** [August 1, 2018, 7:37am UTC](https://discuss.elastic.co/t/could-not-login-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/142488/1 "2018-08-01T07:37:25Z")
![32%20AM](https://us1.discourse-cdn.com/elastic/original/3X/b/2/b21801a9324fa58e9c18fe84ee6011461874adf8.png) I am having this Issue, also I am new for ELK field Please someone could help me out from this , it will be great. I am using Elasticsearch 6.3.2, kibana 6.3.2 and I did not use/install xpack my kibana logs: Aug 01 07:48:22 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:22Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"Unable to revive connection: [http://localhost:9200/](http://localhost:9200/)"} Aug 01 07:48:22 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:22Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"No living connections"} Aug 01 07:48:25 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:25Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"Unable to revive connection: [http://localhost:9200/](http://localhost:9200/)"} Aug 01 07:48:25 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:25Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"No living connections"} Aug 01 07:48:27 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:27Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"Unable to revive connection: [http://localhost:9200/](http://localhost:9200/)"} Aug 01 07:48:27 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:27Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"No living connections"} Aug 01 07:48:30 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:30Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"Unable to revive connection: [http://localhost:9200/](http://localhost:9200/)"} Aug 01 07:48:30 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:30Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"No living connections"} Aug 01 07:48:32 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:32Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"Unable to revive connection: [http://localhost:9200/](http://localhost:9200/)"} Aug 01 07:48:32 localhost.localdomain kibana[3988]: {"type":"log","@timestamp":"2018-08-01T07:48:32Z","tags":["warning","elasticsearch ","admin"],"pid":3988,"message":"No living connections"} root@localhost:~# ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [August 1, 2018, 6:16pm UTC](https://discuss.elastic.co/t/could-not-login-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/142488/2 "2018-08-01T18:16:30Z")
Hi Shree, When you see `Unable to revive connection: http://localhost:9200/` and `No living connections` that means Kibana is configured to use a default address to talk to Elasticsearch, but the Elasticsearch you are running isn't available at that address. It's not an ELK issue, it's just getting 2 services to see each other on a network. You'll need to update the `kibana.yml` file and change the `elasticsearch.url` configuration to the address of your Elasticsearch node. ---
**Author:** ![Shree](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@Shree](https://discuss.elastic.co/u/Shree)\ **Post date:** [August 2, 2018, 7:48am UTC](https://discuss.elastic.co/t/could-not-login-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/142488/3 "2018-08-02T07:48:59Z")
Thank you so much 🙂 I put `localhost` in elasticsearch network host., and I had to change it to `my server ip address.` Also I changed the `elasticsearch.url` in kibana with elasticsearch network address. It works fine now. ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [August 2, 2018, 5:39pm UTC](https://discuss.elastic.co/t/could-not-login-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/142488/4 "2018-08-02T17:39:38Z")
Great! ---
**Author:** ![Shree](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@Shree](https://discuss.elastic.co/u/Shree)\ **Post date:** [August 4, 2018, 8:21am UTC](https://discuss.elastic.co/t/could-not-login-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/142488/5 "2018-08-04T08:21:48Z")
😥 I am getting the same error again. Yesterday I enabled metric beat, and it was working fine but when I opened today it's not working, looks very strange. ``` root@localhost:~# sudo service elasticsearch status ● elasticsearch.service - Elasticsearch Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-08-04 07:57:56 UTC; 22min ago Docs: http://www.elastic.co Process: 3818 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, s tatus=1/FAILURE) Main PID: 3818 (code=exited, status=1/FAILURE) Aug 04 07:57:47 localhost.localdomain systemd[1]: Started Elasticsearch. Aug 04 07:57:56 localhost.localdomain systemd[1]: elasticsearch.service: Main process exited, code=exited, status=1/FAILURE Aug 04 07:57:56 localhost.localdomain systemd[1]: elasticsearch.service: Unit entered failed state. Aug 04 07:57:56 localhost.localdomain systemd[1]: elasticsearch.service: Failed with result 'exit-code'. ``` ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [August 6, 2018, 4:24pm UTC](https://discuss.elastic.co/t/could-not-login-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/142488/6 "2018-08-06T16:24:35Z")
I'm not 100% sure, but it looks like your Elasticsearch service is unable to stay running, and it exits immediately. There should be some clues in Elasticsearch logs, that give more detail beyond the service status. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 3, 2018, 4:24pm UTC](https://discuss.elastic.co/t/could-not-login-login-is-currently-disabled-administrators-should-consult-the-kibana-logs-for-more-details/142488/7 "2018-09-03T16:24:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.