# Kibana Log in disabled

**URL:** <https://discuss.elastic.co/t/kibana-log-in-disabled/132368>\
**Category:** Kibana\
**Created:** [May 17, 2018, 3:27pm UTC](https://discuss.elastic.co/t/kibana-log-in-disabled/132368 "2018-05-17T15:27:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joel\_Alcaraz\_Estragu](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@Joel\_Alcaraz\_Estragu](https://discuss.elastic.co/u/Joel_Alcaraz_Estragu)\
**Post date:** [May 17, 2018, 3:27pm UTC](https://discuss.elastic.co/t/kibana-log-in-disabled/132368/1 "2018-05-17T15:27:43Z")

</div>

Hello there,

I create a docker swarm with 2 stacks (1 with elasticsearch and 1 with kibana), once I deploy them and try to enter on kibana web (URL:5601) it says that the

**login is current disabled. Administrators should consult the Kibana logs for more details.**

my kibana.yml and docker-compose.yml look like this:

```auto
version: '3'
services:
  elasticsearch:
    image: 'docker.elastic.co/elasticsearch/elasticsearch:6.1.4'
    container_name: elastic-docker
    environment:
      - discovery.zen.ping.unicast.hosts=192.168.99.101:9300,192.168.99.102:9300
      - discovery.zen.minimum_master_nodes=1
      - cluster.name=elastic-cluster
      - bootstrap.memory_lock=true
      - ES_JAVA_OPTS=-Xms512m -Xmx512m
    ulimits:
      memlock:
        soft: -1
        hard: -1
    ports:
      - 9200:9200
      - 9300:9300
    deploy:
       mode: replicated
       replicas: 3
    ports:
      - 9200:9200
      - 9300:9300
  kibana:
    image: docker.elastic.co/kibana/kibana:6.1.4
    container_name: kibana-docker
    volumes:
      - ./kibana.yml:/user/share/kibana/config/kibana.yml
    ulimits:
      memlock:
        soft: -1
        hard: -1
    ports:
      - 5601:5601
    deploy:
       mode: replicated
       replicas: 3

```

```auto
server.name: kibana
server.host: "0"
elasticsearch.url: http://elasticsearch:9200
elasticsearch.username: admin
elasticsearch.password: Kibana
xpack.monitoring.ui.container.elasticsearch.enabled: true

```

Don't know why, but when I try to docker-compose up with this same file, the error doesn't apear...

Thank you.

---

<div class="post-metadata">

**Author:** ![Joel\_Alcaraz\_Estragu](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@Joel\_Alcaraz\_Estragu](https://discuss.elastic.co/u/Joel_Alcaraz_Estragu)\
**Post date:** [May 17, 2018, 4:40pm UTC](https://discuss.elastic.co/t/kibana-log-in-disabled/132368/2 "2018-05-17T16:40:26Z")

</div>

I tried to add **xpack.security.enabled: false** to elasticeaerch.yml and kibana.yml\*\*. Same error

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [May 17, 2018, 8:00pm UTC](https://discuss.elastic.co/t/kibana-log-in-disabled/132368/3 "2018-05-17T20:00:40Z")

</div>

Hi,

Can you check if you have x-pack installed?

1. What does [http://localhost:9200/\_xpack/license](http://localhost:9200/_xpack/license) give you about license?
2. Did you generate username/password for es/kibana ?  
[https://www.elastic.co/guide/en/elasticsearch/reference/6.2/installing-xpack-es.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/installing-xpack-es.html) please refer to step 7 in the guide.

Thanks,  
Bhavya

---

<div class="post-metadata">

**Author:** ![Joel\_Alcaraz\_Estragu](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@Joel\_Alcaraz\_Estragu](https://discuss.elastic.co/u/Joel_Alcaraz_Estragu)\
**Post date:** [May 22, 2018, 2:34pm UTC](https://discuss.elastic.co/t/kibana-log-in-disabled/132368/4 "2018-05-22T14:34:50Z")

</div>

1. When i try to connect it shows me this:

```auto
|status|"active"|
|---|---|
|uid|"32369edb-bc32-477e-9843-52710623152e"|
|type|"basic"|
|issue_date|"2018-05-22T14:30:35.106Z"|
|issue_date_in_millis|1526999435106|
|expiry_date|"2018-06-21T14:30:35.106Z"|
|expiry_date_in_millis|1529591435106|
|max_nodes|1000|
|issued_to|"elastic-cluster"|
|issuer|"elasticsearch"|
|start_date_in_millis|-1|

```

1. I though when I use **xpack.security.enabled:false** , don't need the password for kibana. 😣

Thanks

Joel.

---

<div class="post-metadata">

**Author:** ![Joel\_Alcaraz\_Estragu](https://avatars.discourse-cdn.com/v4/letter/j/ac8455/32.png) [@Joel\_Alcaraz\_Estragu](https://discuss.elastic.co/u/Joel_Alcaraz_Estragu)\
**Post date:** [May 22, 2018, 2:54pm UTC](https://discuss.elastic.co/t/kibana-log-in-disabled/132368/5 "2018-05-22T14:54:37Z")

</div>

The real problem here that I don't understand, if I use _docker-compose up_ with the first compose, and kibana.yml, i can connect normally with kibana and it enters without problems in the web app. But when i try _docker stack deploy --compose-file docker-compose.yml test_, it gets stuck with the **login problem**.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 19, 2018, 3:07pm UTC](https://discuss.elastic.co/t/kibana-log-in-disabled/132368/6 "2018-06-19T15:07:18Z")

</div>

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