# Fleet Server only binding to IPv6

**URL:** <https://discuss.elastic.co/t/fleet-server-only-binding-to-ipv6/278213>\
**Category:** Kibana\
**Tags:** fleet\
**Created:** [July 8, 2021, 6:24pm UTC](https://discuss.elastic.co/t/fleet-server-only-binding-to-ipv6/278213 "2021-07-08T18:24:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![omurad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/omurad/32/91292_2.png) [@omurad](https://discuss.elastic.co/u/omurad)\
**Post date:** [July 8, 2021, 6:24pm UTC](https://discuss.elastic.co/t/fleet-server-only-binding-to-ipv6/278213/1 "2021-07-08T18:24:29Z")

</div>

I couldn't get an agent connected to the Fleet Server, so I ran `netstat` on the Fleet Server machine and noticed the port I configured is only bound to IPv6, not IPv4.

My Fleet Server URL is set to `http://0.0.0.0:8220`. I tried changing it to the actual IP of the machine but the issue persisted.

Both firewall and SELinux are disabled at the moment.

How can I get Fleet Server to bind to IPv4?

---

<div class="post-metadata">

**Author:** ![Patrick\_Mueller](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_mueller/32/109425_2.png) [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)\
**Post date:** [July 28, 2021, 6:37pm UTC](https://discuss.elastic.co/t/fleet-server-only-binding-to-ipv6/278213/2 "2021-07-28T18:37:07Z")

</div>

Hello Omar!

As near as I can tell, using `0.0.0.0` as the address will let the fleet server pick the interface to bind to. And using an explicit address should bind to just that address. According to the documentation: [Fleet settings | Fleet User Guide [7.13] | Elastic](https://www.elastic.co/guide/en/fleet/current/fleet-settings.html)

I wonder if there is some Linux networking setting that is for some reason forcing the ipv6 address to get bound. It definitely sounds like a bug if you specify the ipv4 address, and it ends up binding to a different address.

And wondering if the protocol of URL in the config doesn't match how the server is actually running, `http` vs `https`.

If you've exhausted all other options, you could open an issue against the fleet server github repository: [GitHub - elastic/fleet-server: The Fleet server allows managing a fleet of Elastic Agents.](https://github.com/elastic/fleet-server)

---

<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:** [August 25, 2021, 6:37pm UTC](https://discuss.elastic.co/t/fleet-server-only-binding-to-ipv6/278213/3 "2021-08-25T18:37:09Z")

</div>

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