# Unassigned Shards, No Curl Access

**URL:** <https://discuss.elastic.co/t/unassigned-shards-no-curl-access/100702>\
**Category:** Elasticsearch\
**Created:** [September 15, 2017, 4:01pm UTC](https://discuss.elastic.co/t/unassigned-shards-no-curl-access/100702 "2017-09-15T16:01:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MultiplierMultiplier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/multipliermultiplier/32/25063_2.png) [@MultiplierMultiplier](https://discuss.elastic.co/u/MultiplierMultiplier)\
**Post date:** [September 15, 2017, 4:01pm UTC](https://discuss.elastic.co/t/unassigned-shards-no-curl-access/100702/1 "2017-09-15T16:01:57Z")

</div>

Hello,

MY ES cluster state is red and there are 4 unassigned shards. I have read a lot online about solutions to this problem, however they all use Curl commands. Due to my ES instance being on a client site, I can't use curl as when I try to, the connection is pushed externally and then blocked by the firewall. I would ideally like to resolve this issue without having to get the client to change anything. So my question is: Is there anyway to resolve unassigned shards without curl?  
Please note I do have access to the backend of the Ubuntu VM that the ES instance is running on.

Regards,  
G

---

<div class="post-metadata">

**Author:** ![MultiplierMultiplier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/multipliermultiplier/32/25063_2.png) [@MultiplierMultiplier](https://discuss.elastic.co/u/MultiplierMultiplier)\
**Post date:** [September 18, 2017, 2:17pm UTC](https://discuss.elastic.co/t/unassigned-shards-no-curl-access/100702/2 "2017-09-18T14:17:06Z")

</div>

Has anyone got any ideas? I still can't resolve the issue.

Regards,

G

---

<div class="post-metadata">

**Author:** ![MultiplierMultiplier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/multipliermultiplier/32/25063_2.png) [@MultiplierMultiplier](https://discuss.elastic.co/u/MultiplierMultiplier)\
**Post date:** [September 19, 2017, 9:49am UTC](https://discuss.elastic.co/t/unassigned-shards-no-curl-access/100702/3 "2017-09-19T09:49:56Z")

</div>

I solved the issue. The problem was: My VM was trying to use a proxy, so I just commented out the proxy setting in .bashrc, used the curl commands and then uncommented the proxy settings.

G

---

<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:** [October 17, 2017, 9:50am UTC](https://discuss.elastic.co/t/unassigned-shards-no-curl-access/100702/4 "2017-10-17T09:50:41Z")

</div>

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