# Unable to enable x-pack in kibana 7.1.1 docker deployment

**URL:** <https://discuss.elastic.co/t/unable-to-enable-x-pack-in-kibana-7-1-1-docker-deployment/188114>\
**Category:** Elasticsearch\
**Created:** [June 28, 2019, 11:50pm UTC](https://discuss.elastic.co/t/unable-to-enable-x-pack-in-kibana-7-1-1-docker-deployment/188114 "2019-06-28T23:50:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![asrinivasan](https://avatars.discourse-cdn.com/v4/letter/a/b4bc9f/32.png) [@asrinivasan](https://discuss.elastic.co/u/asrinivasan)\
**Post date:** [June 28, 2019, 11:50pm UTC](https://discuss.elastic.co/t/unable-to-enable-x-pack-in-kibana-7-1-1-docker-deployment/188114/1 "2019-06-28T23:50:20Z")

</div>

Unable to enable x-pack in kibana 7.1.1 docker deployment

I get this erro when the pod is starting and then it crashes  
tialized"}  
{"type":"log","@timestamp":"2019-06-28T23:39:59Z","tags":["fatal","root"],"pid":1,"message":"{ Error: ENOENT: no such file or directory, open '/usr/share/kibana/config/certs/elastic-certificate.pem'\n at Object.openSync (fs.js:439:3)\n at readFileSync (fs.js:344:35)\n at readFile (/usr/share/kibana/src/legacy/core\_plugins/elasticsearch/lib/parse\_config.js:46:47)\n at Array.map ()\n at parseConfig (/usr/share/kibana/src/legacy/core\_plugins/elasticsearch/lib/parse\_config.js:101:61)\n at Cluster.createClient (/usr/share/kibana/src/legacy/core\_plugins/elasticsearch/lib/cluster.js:104:85)\n at new Cluster (/usr/share/kibana/src/legacy/core\_plugins/elasticsearch/lib/cluster.js:57:25)\n at Object.create [as createCluster] (/usr/share/kibana/src/legacy/core\_plugins/elasticsearch/lib/create\_clusters.js:26:23)\n at createDataCluster (/usr/share/kibana/src/legacy/core\_plugins/elasticsearch/lib/create\_data\_cluster.js:47:32)\n at Plugin.init [as externalInit] (/usr/share/kibana/src/legacy/core\_plugins/elasticsearch/index.js:63:50)\n at Object.register (/usr/share/kibana/src/legacy/server/plugins/lib/plugin.js:71:20)\n at internals.Server.register (/usr/share/kibana/node\_modules/hapi/lib/server.js:431:35)\n at Plugin.init (/usr/share/kibana/src/legacy/server/plugins/lib/plugin.js:75:28)\n at Plugin.init (/usr/share/kibana/node\_modules/lodash/index.js:7407:25)\n at callPluginHook (/usr/share/kibana/src/legacy/server/plugins/lib/call\_plugin\_hook.js:37:25)\n errno: -2,\n syscall: 'open',\n code: 'ENOENT',\n path: '/usr/share/kibana/config/certs/elastic-certificate.pem' }"}

FATAL Error: ENOENT: no such file or directory, open '/usr/share/kibana/config/certs/elastic-certificate.pem

secret is present and also seems to mount on the pod , not sure why it complains

elastic-certificate-pem Opaque 1 23

bash-4.2$ ls -al /usr/share/kibana/config/certs/  
total 4  
drwxrwsrwt 4 root kibana 120 Jun 28 23:48 .  
drwxrwsr-x 1 kibana root 4096 Jun 28 23:48 ..  
drwxr-sr-x 2 root kibana 60 Jun 28 23:48 ..2019\_06\_28\_23\_48\_48.925865630  
lrwxrwxrwx 1 root root 31 Jun 28 23:48 ..data -\> ..2019\_06\_28\_23\_48\_48.925865630  
lrwxrwxrwx 1 root root 30 Jun 28 23:48 elastic-certificate-pem -\> ..data/elastic-certificate-pem  
drwxrwsrwt 3 root kibana 120 Jun 28 23:48 kibana  
bash-4.2$

Not sure why it cannot see the file

---

<div class="post-metadata">

**Author:** ![asrinivasan](https://avatars.discourse-cdn.com/v4/letter/a/b4bc9f/32.png) [@asrinivasan](https://discuss.elastic.co/u/asrinivasan)\
**Post date:** [July 2, 2019, 12:17am UTC](https://discuss.elastic.co/t/unable-to-enable-x-pack-in-kibana-7-1-1-docker-deployment/188114/2 "2019-07-02T00:17:09Z")

</div>

was able to resolve had to have the file name ..data/elastic-certificate.pem

---

<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:** [July 30, 2019, 12:17am UTC](https://discuss.elastic.co/t/unable-to-enable-x-pack-in-kibana-7-1-1-docker-deployment/188114/3 "2019-07-30T00:17:15Z")

</div>

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