# √Fleet managed Elastic Agent listens on port 6791 by default with not activating http endpoint monitoring

**URL:** <https://discuss.elastic.co/t/fleet-managed-elastic-agent-listens-on-port-6791-by-default-with-not-activating-http-endpoint-monitoring/371843>\
**Category:** Beats\
**Tags:** fleet\
**Created:** [December 11, 2024, 2:08pm UTC](https://discuss.elastic.co/t/fleet-managed-elastic-agent-listens-on-port-6791-by-default-with-not-activating-http-endpoint-monitoring/371843 "2024-12-11T14:08:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Markus\_Muhr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markus_muhr/32/139813_2.png) [@Markus\_Muhr](https://discuss.elastic.co/u/Markus_Muhr)\
**Post date:** [December 11, 2024, 2:08pm UTC](https://discuss.elastic.co/t/fleet-managed-elastic-agent-listens-on-port-6791-by-default-with-not-activating-http-endpoint-monitoring/371843/1 "2024-12-11T14:08:32Z")

</div>

Hi there,

we have experienced an odd behaviour with http endpoint monitoring which defaults to port 6791.

We manage our agents via fleet and we haven't activated the http endpoint monitoring. Nevertheless, the agent is listening on the port. When activating it in the fleet and explicitly use a different port, the agent doesn't listen on 6791 anymore.

We assumed that not activating the http endpoint monitoring the agent won't activate that feature. We encountered this problem because of a port collision with our backup solution.

Is this a bug? Should we report it?

---

<div class="post-metadata">

**Author:** ![strawgate](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/strawgate/32/131008_2.png) [@strawgate](https://discuss.elastic.co/u/strawgate)\
**Post date:** [December 11, 2024, 2:22pm UTC](https://discuss.elastic.co/t/fleet-managed-elastic-agent-listens-on-port-6791-by-default-with-not-activating-http-endpoint-monitoring/371843/2 "2024-12-11T14:22:31Z")

</div>

Sorry to hear you're running into this.

There is an open bug [here](https://github.com/elastic/kibana/issues/201459) that looks like this issue -- it has some activity as of last week

By default it should be listening only on `localhost` so it should not be accessible over the network