# Coordinator fails to retrieve cluster state when proxy role is not assigned

**URL:** <https://discuss.elastic.co/t/coordinator-fails-to-retrieve-cluster-state-when-proxy-role-is-not-assigned/73506>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [February 1, 2017, 11:17am UTC](https://discuss.elastic.co/t/coordinator-fails-to-retrieve-cluster-state-when-proxy-role-is-not-assigned/73506 "2017-02-01T11:17:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [February 1, 2017, 11:17am UTC](https://discuss.elastic.co/t/coordinator-fails-to-retrieve-cluster-state-when-proxy-role-is-not-assigned/73506/1 "2017-02-01T11:17:51Z")

</div>

I would like to get help with how to diagnose below issue.

I have installed Coordinator node (Coordinator and Director) and Proxy node separately.  
However, when I login to admin console , it looks like below.

 ![](https://us1.discourse-cdn.com/elastic/original/2X/d/d1739cf6249501a18ac804f26e143ae64a27b83f.PNG)

It looks like the admin console API returns 500 internal server error.

`http://xxx.xxx.xxx.xxx:12300/api/v1/elasticsearch/clusters-*/_search Failed to load resource: the server responded with a status of 500 (Internal Server Error)`

Referencing the [Topology plan](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-planning.html#ece-topology) , I have excluded the **proxy** on the coordinator node as below.

 ![](https://us1.discourse-cdn.com/elastic/original/2X/a/a92cce44a26be74a2c973f00ccc0d68db64c6701.PNG)

- runner-Manager1 is the node which error is occurring.

Is there a log which I can look at to get more insight with the error?

---

<div class="post-metadata">

**Author:** ![uricohen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uricohen/32/9776_2.png) [@uricohen](https://discuss.elastic.co/u/uricohen)\
**Post date:** [February 1, 2017, 11:50am UTC](https://discuss.elastic.co/t/coordinator-fails-to-retrieve-cluster-state-when-proxy-role-is-not-assigned/73506/2 "2017-02-01T11:50:42Z")

</div>

Hi @YuWatanabe

This is a known issue with Alpha4 where the API server tries to connect to the backing Elasticsearch cluster using the proxy, and assumes the proxy always resides on the initial host (in your case it's runner-Manager1).  
This issue will be resolved in the upcoming beta release.

HTH  
Uri

---

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [February 2, 2017, 5:40am UTC](https://discuss.elastic.co/t/coordinator-fails-to-retrieve-cluster-state-when-proxy-role-is-not-assigned/73506/3 "2017-02-02T05:40:00Z")

</div>

@uricohen

Good to here. Thanks.

---

<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:** [February 5, 2017, 5:39am UTC](https://discuss.elastic.co/t/coordinator-fails-to-retrieve-cluster-state-when-proxy-role-is-not-assigned/73506/4 "2017-02-05T05:39:59Z")

</div>

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