# Permission denied (os:windows)

**URL:** <https://discuss.elastic.co/t/permission-denied-os-windows/304923>\
**Category:** Elasticsearch\
**Created:** [May 17, 2022, 11:07am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923 "2022-05-17T11:07:49Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![RohitBR\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitbr_k/32/103666_2.png) [@RohitBR\_K](https://discuss.elastic.co/u/RohitBR_K)\
**Post date:** [May 17, 2022, 11:07am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/1 "2022-05-17T11:07:49Z")

</div>

Am starting Elasticsearch like this  
`cd elasticsearch/bin/elasticsearch.bat`  
but am getting permission denied when am accessing one of my es documents through my API.  
am not understanding what's the issue here . Am using windows as my operating system.

If anyone knows the solution , please help me

---

<div class="post-metadata">

**Author:** ![sudhagar\_ramesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sudhagar_ramesh/32/105673_2.png) [@sudhagar\_ramesh](https://discuss.elastic.co/u/sudhagar_ramesh)\
**Post date:** [May 17, 2022, 12:27pm UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/2 "2022-05-17T12:27:32Z")

</div>

Hello @RohitBR_K  
I believe you have placed the elastisearch in C drive's permission required folder.

To sort out this you can two things:

1. if you have admin rights launch the command prompt as administrator and then execute this command
2. if you don't have admin rights then move this Elasticsearch folder to some other location and execute the command.

Keep Posted!!!Thanks!!!

---

<div class="post-metadata">

**Author:** ![RohitBR\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitbr_k/32/103666_2.png) [@RohitBR\_K](https://discuss.elastic.co/u/RohitBR_K)\
**Post date:** [May 18, 2022, 1:34pm UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/3 "2022-05-18T13:34:41Z")

</div>

not working bro

---

<div class="post-metadata">

**Author:** ![sudhagar\_ramesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sudhagar_ramesh/32/105673_2.png) [@sudhagar\_ramesh](https://discuss.elastic.co/u/sudhagar_ramesh)\
**Post date:** [May 18, 2022, 1:47pm UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/4 "2022-05-18T13:47:48Z")

</div>

Could you provide some screenshots on how you are accessing your es documents through your api  
with the error message

---

<div class="post-metadata">

**Author:** ![RohitBR\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitbr_k/32/103666_2.png) [@RohitBR\_K](https://discuss.elastic.co/u/RohitBR_K)\
**Post date:** [May 18, 2022, 2:00pm UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/5 "2022-05-18T14:00:12Z")

</div>

![image](https://us1.discourse-cdn.com/elastic/original/3X/c/5/c509297ba261d7fda841c0a9d472358a8c305ff9.png)  
this is it !

---

<div class="post-metadata">

**Author:** ![sudhagar\_ramesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sudhagar_ramesh/32/105673_2.png) [@sudhagar\_ramesh](https://discuss.elastic.co/u/sudhagar_ramesh)\
**Post date:** [May 18, 2022, 2:17pm UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/6 "2022-05-18T14:17:34Z")

</div>

Could you try using the same command with  
Cat api

GET \_cat//

---

<div class="post-metadata">

**Author:** ![RohitBR\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitbr_k/32/103666_2.png) [@RohitBR\_K](https://discuss.elastic.co/u/RohitBR_K)\
**Post date:** [May 18, 2022, 2:19pm UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/7 "2022-05-18T14:19:24Z")

</div>

sorry I didn't get that. Can you please enlarge this

---

<div class="post-metadata">

**Author:** ![sudhagar\_ramesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sudhagar_ramesh/32/105673_2.png) [@sudhagar\_ramesh](https://discuss.elastic.co/u/sudhagar_ramesh)\
**Post date:** [May 19, 2022, 2:29am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/8 "2022-05-19T02:29:31Z")

</div>

@RohitBR_K  
Could you try using the same command with  
Cat api

`GET _cat/<index-name>/<doc-name>?v=true&s=index`

**Reference:**

> **[cat indices API | Elasticsearch Guide \[8.2\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/cat-indices.html)**

---

<div class="post-metadata">

**Author:** ![RohitBR\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitbr_k/32/103666_2.png) [@RohitBR\_K](https://discuss.elastic.co/u/RohitBR_K)\
**Post date:** [May 19, 2022, 8:37am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/9 "2022-05-19T08:37:48Z")

</div>

from cmd ?

---

<div class="post-metadata">

**Author:** ![sudhagar\_ramesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sudhagar_ramesh/32/105673_2.png) [@sudhagar\_ramesh](https://discuss.elastic.co/u/sudhagar_ramesh)\
**Post date:** [May 19, 2022, 9:12am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/10 "2022-05-19T09:12:10Z")

</div>

@RohitBR_K

yes, using curl command

`curl -X GET "http://localhost:9200/<index>/_search?pretty" -u "<your-elastic-username>"`

if you are accessing your cluster using credentials else the same command without credentials

`curl -X GET "http://localhost:9200/<index>/_search?pretty`

---

<div class="post-metadata">

**Author:** ![RohitBR\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitbr_k/32/103666_2.png) [@RohitBR\_K](https://discuss.elastic.co/u/RohitBR_K)\
**Post date:** [May 19, 2022, 9:15am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/11 "2022-05-19T09:15:49Z")

</div>

sorry , not working this bro

---

<div class="post-metadata">

**Author:** ![sudhagar\_ramesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sudhagar_ramesh/32/105673_2.png) [@sudhagar\_ramesh](https://discuss.elastic.co/u/sudhagar_ramesh)\
**Post date:** [May 19, 2022, 9:18am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/12 "2022-05-19T09:18:26Z")

</div>

Could you share the output of the above command

---

<div class="post-metadata">

**Author:** ![RohitBR\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitbr_k/32/103666_2.png) [@RohitBR\_K](https://discuss.elastic.co/u/RohitBR_K)\
**Post date:** [May 19, 2022, 9:20am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/13 "2022-05-19T09:20:56Z")

</div>

yes am getting that using the command you provide , but I wonder , why am getting that error when calling through API

---

<div class="post-metadata">

**Author:** ![sudhagar\_ramesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sudhagar_ramesh/32/105673_2.png) [@sudhagar\_ramesh](https://discuss.elastic.co/u/sudhagar_ramesh)\
**Post date:** [May 19, 2022, 9:23am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/14 "2022-05-19T09:23:04Z")

</div>

@RohitBR_K  
I believe its more of a thing that needs to be checked in Django level which needs to focus on configuration part

---

<div class="post-metadata">

**Author:** ![RohitBR\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rohitbr_k/32/103666_2.png) [@RohitBR\_K](https://discuss.elastic.co/u/RohitBR_K)\
**Post date:** [May 19, 2022, 9:33am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/15 "2022-05-19T09:33:48Z")

</div>

hmm..ok

---

<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 16, 2022, 9:34am UTC](https://discuss.elastic.co/t/permission-denied-os-windows/304923/16 "2022-06-16T09:34:20Z")

</div>

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