# Kibana asking for Enrollment Token when xpack.security.enabled: false in Elasticsearch **URL:** \ **Category:** Kibana\ **Created:** [April 11, 2022, 2:47pm UTC](https://discuss.elastic.co/t/kibana-asking-for-enrollment-token-when-xpack-security-enabled-false-in-elasticsearch/302118 "2022-04-11T14:47:19Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [April 15, 2022, 4:12am UTC](https://discuss.elastic.co/t/kibana-asking-for-enrollment-token-when-xpack-security-enabled-false-in-elasticsearch/302118/2 "2022-04-15T04:12:13Z")
You have two options: 1. You click on "Configure manually" right below the input box for the enrollment token and you manually add the Elasticsearch HTTP address, such as `http://172.17.0.2:9200` 2. Start Kibana by passing in the ELASTICSEARCH\_HOSTS env variable, i,e, `-e "ELASTICSEARCH_HOSTS=http://es01-test:9200"` In theory, you can always pass `-e "INTERACTIVESETUP_ENABLED=false"` to disable the interactive setup mode but in this case, if you don't configure anything else, kibana will try to connect to localhost to find Elasticsearch on 9200. When in k8s or docker, that `localhost` is the container where kibana runs so this will fail. It would work if both kibana and Elasticsearch run from archives on the same host. HTH --- _[View the full topic](https://discuss.elastic.co/t/kibana-asking-for-enrollment-token-when-xpack-security-enabled-false-in-elasticsearch/302118)._