# Running Fleet Server on localhost
**URL:** https://discuss.elastic.co/t/running-fleet-server-on-localhost/382174
**Category:** Elastic Agent
**Tags:** fleet
**Created:** [September 23, 2025, 3:11pm UTC](https://discuss.elastic.co/t/running-fleet-server-on-localhost/382174 "2025-09-23T15:11:34Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@primote](https://discuss.elastic.co/u/primote)
#### Post date: [September 23, 2025, 3:11pm UTC](https://discuss.elastic.co/t/running-fleet-server-on-localhost/382174/1 "2025-09-23T15:11:34Z")
Is it possible to run a Fleet Server on the same host as Elastic and Kibana?
I`m using basic Elasticsearch and Kibana on my VM and I would like to setup Fleet and Agents for use with Elastic Security
How can i configure my Fleet Server Host URL and install the Fleet Server for this kind of deployment? Is there a better way to do this?
I`ve been trying to configure [https://127.0.0.1:8220](https://127.0.0.1:8220) as my URL but somehow during installation the requests of my fleet-server go to 10.50.0.124, an unreachable host.
---
### Author:  [@nvanalphen](https://discuss.elastic.co/u/nvanalphen)
#### Post date: [September 24, 2025, 9:36am UTC](https://discuss.elastic.co/t/running-fleet-server-on-localhost/382174/2 "2025-09-24T09:36:02Z")
It can be done. We are running a single node instance on a VM similar to what you are trying to do.
We do not use 127.0.0.1 (=localhost) however and I think that’s where your issues start. If you want to add agents to the Fleet Server other than the VM itself, you will need to use a different IP address.
We tried to use a private IP address, but ran into some routing issues when connecting agents, so we moved to using a public IP address and a publicly registerred hostname and it all works like a charm.
Fleet Server collects logs from several other VMs, the firewall and our M365 tenant