# Fleet Server invalid argument “tcp://10.233.110.49:8220” for “–fleet-server-port”

**URL:** <https://discuss.elastic.co/t/fleet-server-invalid-argument-tcp-10-233-110-49-8220-for-fleet-server-port/317017>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [October 19, 2022, 2:38pm UTC](https://discuss.elastic.co/t/fleet-server-invalid-argument-tcp-10-233-110-49-8220-for-fleet-server-port/317017 "2022-10-19T14:38:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [October 19, 2022, 2:38pm UTC](https://discuss.elastic.co/t/fleet-server-invalid-argument-tcp-10-233-110-49-8220-for-fleet-server-port/317017/1 "2022-10-19T14:38:13Z")

</div>

Even with ECK 2.4, I'm still able to reproduce this error. [Fleet Server invalid argument "tcp://10.233.110.49:8220" for "--fleet-server-port"](https://discuss.elastic.co/t/fleet-server-invalid-argument-tcp-10-233-110-49-8220-for-fleet-server-port/293566). I did find that it only appears to happen when I create a service with the same name as the agent. So in this case the agent name is `fleet-server` and the Service of type Load Balancer is also named `fleet-server`. If I don't have the load balancer or use a different name, everything works just fine. Thoughts??

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [October 25, 2022, 12:28pm UTC](https://discuss.elastic.co/t/fleet-server-invalid-argument-tcp-10-233-110-49-8220-for-fleet-server-port/317017/2 "2022-10-25T12:28:57Z")

</div>

I figured it out. Its because K8S automatically injects ENV vars of services and since I have a service named `fleet-server` it creates an env var called `FLEET_SERVER_PORT` which is an actual var from fleet server and causes the conflict.

---

<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:** [November 22, 2022, 12:29pm UTC](https://discuss.elastic.co/t/fleet-server-invalid-argument-tcp-10-233-110-49-8220-for-fleet-server-port/317017/3 "2022-11-22T12:29:53Z")

</div>

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