# Can't connect to COORDINATOR\_HOST when using emergency role token

**URL:** <https://discuss.elastic.co/t/cant-connect-to-coordinator-host-when-using-emergency-role-token/221218>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [February 27, 2020, 11:33am UTC](https://discuss.elastic.co/t/cant-connect-to-coordinator-host-when-using-emergency-role-token/221218 "2020-02-27T11:33:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Riley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_riley/32/56782_2.png) [@Andrew\_Riley](https://discuss.elastic.co/u/Andrew_Riley)\
**Post date:** [February 27, 2020, 11:33am UTC](https://discuss.elastic.co/t/cant-connect-to-coordinator-host-when-using-emergency-role-token/221218/1 "2020-02-27T11:33:51Z")

</div>

I'm trying to recover my ECE instance after losing my co-ordinator server.

The information on [Using Emergency Roles token](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-troubleshooting-emergency.html) says to run

> [@](#):
>
> install --coordinator-host 192.168.50.10 --roles-token {token}

specifying the old co-ordinator host, but the installation validation output says;

Checking coordinator connectivity ... FAILED  
Can't connect COORDINATOR\_HOST [ip.address] connection refused

I don't understand this message, because losing the coordinator host is why I'm using the emergency all roles token. What am I misunderstanding?

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [February 27, 2020, 2:38pm UTC](https://discuss.elastic.co/t/cant-connect-to-coordinator-host-when-using-emergency-role-token/221218/2 "2020-02-27T14:38:00Z")

</div>

Hmm the docs aren't worded great here ... although it says "COORDINATOR\_HOST", in practice it means "an ECE host with the director role".

If you lose 100% of your nodes running a director, then the ECE is gone forever unfortunately .. that's the reason step 2 after install is making ECE HA by adding additional directors

(The main purpose for the emergency token in practice is if you lose all your coordinators - since then the system is happy except that you've lost API access, ie the ability to create tokens)

If you have other director nodes still alive then use their IPs instead

(if you have 3 directors and have lost 2 of them, then the situation can be rectified but it requires a bit of hand editing of files)

---

<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:** [March 12, 2020, 2:38pm UTC](https://discuss.elastic.co/t/cant-connect-to-coordinator-host-when-using-emergency-role-token/221218/3 "2020-03-12T14:38:00Z")

</div>

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