# Incorrect CloudID - Port ignored // Bug?

**URL:** <https://discuss.elastic.co/t/incorrect-cloudid-port-ignored-bug/173195>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [March 20, 2019, 5:17pm UTC](https://discuss.elastic.co/t/incorrect-cloudid-port-ignored-bug/173195 "2019-03-20T17:17:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![infomaniac](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/infomaniac/32/24996_2.png) [@infomaniac](https://discuss.elastic.co/u/infomaniac)\
**Post date:** [March 20, 2019, 5:17pm UTC](https://discuss.elastic.co/t/incorrect-cloudid-port-ignored-bug/173195/1 "2019-03-20T17:17:08Z")

</div>

I have noticed the CloudID is not showing correctly (at least in the UI).

Elasticsearch Endpoint URL: `https://c5d47b9145994b8faebf510cebe7e3dc.elastic.hs.coop.ch:9243`  
Kibana Endpoint URL: `https://778494e02130436c8d517a97e191f73a.elastic.hs.coop.ch:9243`

Example CloudID:  
`TestCluster:ZWxhc3RpYy5ocy5jb29wLmNoJGM1ZDQ3YjkxNDU5OTRiOGZhZWJmNTEwY2ViZTdlM2RjJDc3ODQ5NGUwMjEzMDQzNmM4ZDUxN2E5N2UxOTFmNzNh`

This decodes (base64) to `elastic.hs.coop.ch$c5d47b9145994b8faebf510cebe7e3dc$778494e02130436c8d517a97e191f73a` which is **`host`** $ **`elasticsearchID`** $ **`kibanaID`**

If you use this CloudID in Beats or Logstash, it will fail because it cannot connect to `https://c5d47b9145994b8faebf510cebe7e3dc.elastic.hs.coop.ch` ( **without** port 9243).

I assume this is a bug?

---

<div class="post-metadata">

**Author:** ![zanbel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zanbel/32/20678_2.png) [@zanbel](https://discuss.elastic.co/u/zanbel)\
**Post date:** [March 20, 2019, 5:58pm UTC](https://discuss.elastic.co/t/incorrect-cloudid-port-ignored-bug/173195/2 "2019-03-20T17:58:47Z")

</div>

Thanks for opening the issue!  
As you noticed, we currently don't set the correct port so it defaults to 443. If you have a reverse proxy or load-balancer in front of ECE proxy layer (recommended regardless) you can redirect request to the correct port.

We are aware of this issue and the team is working on a fix that should be available shortly. The new implementation will allow you to set the external port and that value will be used in the cloud id.

---

<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:** [March 20, 2019, 6:01pm UTC](https://discuss.elastic.co/t/incorrect-cloudid-port-ignored-bug/173195/3 "2019-03-20T18:01:16Z")

</div>

> [@zanbel](#):
>
> If you have a reverse proxy or load-balancer in front of ECE proxy layer (recommended regardless) you can redirect request to the correct port.

(or you can use `iptables` on the proxy hosts to map from `443` to `9243`, that's a common solution .. again: arguably preferable anyway, there's no reason to be using non-standard ports like 9243 for _public_ access to clusters' HTTP interfaces)

---

<div class="post-metadata">

**Author:** ![infomaniac](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/infomaniac/32/24996_2.png) [@infomaniac](https://discuss.elastic.co/u/infomaniac)\
**Post date:** [March 21, 2019, 11:58am UTC](https://discuss.elastic.co/t/incorrect-cloudid-port-ignored-bug/173195/4 "2019-03-21T11:58:33Z")

</div>

That's great news.

---

<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:** [April 4, 2019, 11:58am UTC](https://discuss.elastic.co/t/incorrect-cloudid-port-ignored-bug/173195/5 "2019-04-04T11:58:35Z")

</div>

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