# Without the write permission of the kibana directory, how to launch kibana properly

**URL:** <https://discuss.elastic.co/t/without-the-write-permission-of-the-kibana-directory-how-to-launch-kibana-properly/344543>\
**Category:** Kibana\
**Created:** [October 6, 2023, 4:51pm UTC](https://discuss.elastic.co/t/without-the-write-permission-of-the-kibana-directory-how-to-launch-kibana-properly/344543 "2023-10-06T16:51:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lingran\_Xiao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lingran_xiao/32/126312_2.png) [@Lingran\_Xiao](https://discuss.elastic.co/u/Lingran_Xiao)\
**Post date:** [October 6, 2023, 4:51pm UTC](https://discuss.elastic.co/t/without-the-write-permission-of-the-kibana-directory-how-to-launch-kibana-properly/344543/1 "2023-10-06T16:51:50Z")

</div>

Hi, I don't have the write permission of the kibana-8.7.1 directory, but my group want me to finish the deployment of kibana. I specify the config directory by using the environment variable KBN\_PATH\_CONF.

And when I tried to launch kibana, with path.data set as /home/phoebus3/XIAOL/test/elk-deployment/C2/data/elk/kibana, I got quite a few errors:

```auto
Oct 05 16:13:45 [ctlpc9.aps.anl.gov](http://ctlpc9.aps.anl.gov/) kibana[1100326]: [2023-10-05T16:13:45.753-05:00][ERROR][plugins.interactiveSetup.verification] Failed to write verification code to /home/phoebus3/XIAOL/test/elk-deployment/C2/elk-zip/kibana-8.7.1/data/verification_code: EACCES: permission denied, open '/home/phoebus3/XIAOL/test/elk-deployment/C2/elk-zip/kibana-8.7.1/data/verification_code'.

Oct 06 11:39:09 [ctlpc9.aps.anl.gov](http://ctlpc9.aps.anl.gov/) kibana[2165054]: [2023-10-06T11:39:09.335-05:00][ERROR][plugins.screenshotting] Error: EACCES: permission denied, mkdtemp '/home/phoebus3/XIAOL/test/elk-deployment/C2/elk-zip/kibana-8.7.1/data/chromium-XXXXXX' Oct 06 11:39:09 kibana[2165054]: at Object.mkdtempSync (node:fs:2797:3) Oct 06 11:39:09 kibana[2165054]: at new HeadlessChromiumDriverFactory (/home/phoebus3/XIAOL/test/elk-deployment/C2/elk-zip/kibana-8.7.1/x-pack/plugins/screenshotting/server/browsers/chromium/driver_factory/index.js:62:36) Oct 06 11:39:09 kibana[2165054]: at /home/phoebus3/XIAOL/test/elk-deployment/C2/elk-zip/kibana-8.7.1/x-pack/plugins/screenshotting/server/plugin.js:46:14 Oct 06 11:39:09 kibana[2165054]: at runMicrotasks (<anonymous>) Oct 06 11:39:09 kibana[2165054]: at processTicksAndRejections (node:internal/process/task_queues:96:5)

```

It seems that kiban was still trying to write contents inside its own directory and ignored the path.data. I wonder how to solve this problem and launch kibana properly without the write permission inside the kibana directory. Thanks a lot for your help.

Best,  
Lingran

---

<div class="post-metadata">

**Author:** ![Lingran\_Xiao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lingran_xiao/32/126312_2.png) [@Lingran\_Xiao](https://discuss.elastic.co/u/Lingran_Xiao)\
**Post date:** [October 11, 2023, 3:17pm UTC](https://discuss.elastic.co/t/without-the-write-permission-of-the-kibana-directory-how-to-launch-kibana-properly/344543/2 "2023-10-11T15:17:25Z")

</div>

I've found the previous similar issue [here](https://github.com/elastic/kibana/issues/142865) , and the solution [here](https://github.com/elastic/kibana/pull/157659). I think kibana 8.9 has solved this problem but I've not tested yet.

---

<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:** [November 8, 2023, 3:18pm UTC](https://discuss.elastic.co/t/without-the-write-permission-of-the-kibana-directory-how-to-launch-kibana-properly/344543/3 "2023-11-08T15:18:02Z")

</div>

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