# Kibana freezes in "Kibana server is not ready yet" after activating xpack.security

**URL:** <https://discuss.elastic.co/t/kibana-freezes-in-kibana-server-is-not-ready-yet-after-activating-xpack-security/257699>\
**Category:** Kibana\
**Tags:** elastic-stack-security\
**Created:** [December 4, 2020, 8:52pm UTC](https://discuss.elastic.co/t/kibana-freezes-in-kibana-server-is-not-ready-yet-after-activating-xpack-security/257699 "2020-12-04T20:52:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jh0mil](https://avatars.discourse-cdn.com/v4/letter/j/9de053/32.png) [@jh0mil](https://discuss.elastic.co/u/jh0mil)\
**Post date:** [December 4, 2020, 8:52pm UTC](https://discuss.elastic.co/t/kibana-freezes-in-kibana-server-is-not-ready-yet-after-activating-xpack-security/257699/1 "2020-12-04T20:52:25Z")

</div>

When i set true the opcion xpack.security.enabled the service stay frozen in "Kibana server is not ready yet".

This is the logs of Kibana

> log [19:22:35.884] [info][plugins-service] Plugin "visTypeXy" is disabled.  
> log [19:22:35.892] [info][plugins-service] Plugin "auditTrail" is disabled.  
> log [19:22:35.958] [warning][config][deprecation] Setting [elasticsearch.username] to "kibana" is deprecated. You should use the "kibana \_system" user instead.  
> log [19:22:35.959] [warning][config][deprecation] Config key [monitoring.cluster\_alerts.email\_notifications.email\_address] will be requi red for email notifications to work in 8.0."  
> log [19:22:35.960] [warning][config][deprecation] Setting [monitoring.username] to "kibana" is deprecated. You should use the "kibana\_sy stem" user instead.  
> log [19:22:36.172] [info][plugins-system] Setting up [96] plugins: [taskManager,licensing,globalSearch,globalSearchProviders,code,usageC ollection,xpackLegacy,telemetryCollectionManager,telemetry,telemetryCollectionXpack,kibanaUsageCollection,securityOss,mapsLegacy,newsfeed,ki banaLegacy,translations,share,legacyExport,embeddable,uiActionsEnhanced,expressions,data,home,observability,cloud,console,consoleExtensions, apmOss,searchprofiler,painlessLab,grokdebugger,management,indexPatternManagement,advancedSettings,fileUpload,savedObjects,dashboard,visualiz ations,visTypeVega,visTypeTimelion,timelion,features,upgradeAssistant,security,snapshotRestore,encryptedSavedObjects,ingestManager,indexMana gement,remoteClusters,crossClusterReplication,indexLifecycleManagement,enterpriseSearch,dashboardMode,beatsManagement,transform,ingestPipeli nes,maps,licenseManagement,graph,dataEnhanced,visTypeTable,visTypeMarkdown,tileMap,regionMap,inputControlVis,visualize,esUiShared,bfetch,can vas,charts,lens,visTypeVislib,visTypeTimeseries,rollup,visTypeTagcloud,visTypeMetric,watcher,discover,discoverEnhanced,savedObjectsManagemen t,spaces,reporting,lists,eventLog,actions,case,alerts,stackAlerts,triggersActionsUi,ml,securitySolution,infra,monitoring,logstash,apm,uptime]  
> log [19:22:36.560] [warning][config][plugins][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions fr om being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml  
> log [19:22:36.561] [warning][config][plugins][security] Session cookies will be transmitted over insecure connections. This is not recom mended.  
> log [19:22:36.597] [warning][config][encryptedSavedObjects][plugins] Generating a random key for xpack.encryptedSavedObjects.encryptionK ey. To be able to decrypt encrypted saved objects attributes after restart, please set xpack.encryptedSavedObjects.encryptionKey in kibana.y ml  
> log [19:22:36.604] [warning][ingestManager][plugins] Fleet APIs are disabled due to the Encrypted Saved Objects plugin using an ephemera l encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml.  
> log [19:22:36.743] [warning][config][plugins][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.reporting.encryptionKey in kibana.yml  
> log [19:22:36.746] [info][config][plugins][reporting] Chromium sandbox provides an additional layer of protection, and is supported for Linux Ubuntu 18.04 OS. Automatically enabling Chromium sandbox.  
> log [19:22:36.761] [warning][actions][actions][plugins] APIs are disabled due to the Encrypted Saved Objects plugin using an ephemeral e ncryption key. Please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml.  
> log [19:22:36.786] [warning][alerting][alerts][plugins][plugins] APIs are disabled due to the Encrypted Saved Objects plugin using an ep hemeral encryption key. Please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml.  
> log [19:22:36.940] [info][monitoring][monitoring][plugins] config sourced from: production cluster  
> log [19:22:37.244] [info][savedobjects-service] Waiting until all Elasticsearch nodes are compatible with Kibana before starting saved o bjects migrations...  
> log [19:22:37.264] [error][elasticsearch][monitoring] Request error, retrying  
> GET [http://10.0.0.4:9200/\_xpack](http://10.0.0.4:9200/_xpack) =\> connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:37.267] [warning][elasticsearch][monitoring] Unable to revive connection: [http://10.0.0.4:9200/](http://10.0.0.4:9200/)  
> log [19:22:37.267] [warning][elasticsearch][monitoring] No living connections  
> log [19:22:37.268] [warning][licensing][plugins] License information could not be obtained from Elasticsearch due to Error: No Living co nnections error  
> log [19:22:37.275] [warning][monitoring][monitoring][plugins] X-Pack Monitoring Cluster Alerts will not be available: No Living connecti ons  
> log [19:22:37.277] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:37.305] [error][savedobjects-service] Unable to retrieve version information from Elasticsearch nodes.  
> log [19:22:39.760] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:42.262] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:44.763] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:47.263] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:49.766] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:52.273] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:54.770] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:57.270] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:59.774] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:23:02.275] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:23:04.777] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:23:07.259] [warning][elasticsearch][monitoring] Unable to revive connection: [http://10.0.0.4:9200/](http://10.0.0.4:9200/)  
> log [19:23:07.260] [warning][elasticsearch][monitoring] No living connections  
> log [19:23:07.260] [warning][licensing][plugins] License information could not be obtained from Elasticsearch due to Error: No Living connections error

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [December 7, 2020, 7:58am UTC](https://discuss.elastic.co/t/kibana-freezes-in-kibana-server-is-not-ready-yet-after-activating-xpack-security/257699/2 "2020-12-07T07:58:36Z")

</div>

> [@jh0mil](#):
>
> When i set true the opcion xpack.security.enabled the service stay frozen in "Kibana server is not ready yet".

> og [19:22:37.277] [error][data][elasticsearch] [ConnectionError]: connect ECONNREFUSED 10.0.0.4:9200  
> log [19:22:37.305] [error][savedobjects-service] Unable to retrieve version information from Elasticsearch nodes.

That's the issue here, but it's hard to tell what you're doing exactly:

- Did enable security in Elasticsearch or Kibana?
- If in Kibana, do you connect to Elasticsearch that also has Security enabled?
- Did you configure `elasticseach.username/password` in `kibana.yml`?

The more information about your setup you can provide, the more likely we'll be able to help.

Oleg

---

<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:** [January 4, 2021, 7:58am UTC](https://discuss.elastic.co/t/kibana-freezes-in-kibana-server-is-not-ready-yet-after-activating-xpack-security/257699/3 "2021-01-04T07:58:46Z")

</div>

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