# Fleet Server 8.8.1 on prems boot issue

**URL:** <https://discuss.elastic.co/t/fleet-server-8-8-1-on-prems-boot-issue/337312>\
**Category:** Elastic Security\
**Created:** [June 30, 2023, 12:47pm UTC](https://discuss.elastic.co/t/fleet-server-8-8-1-on-prems-boot-issue/337312 "2023-06-30T12:47:42Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![matled](https://avatars.discourse-cdn.com/v4/letter/m/ba8739/32.png) [@matled](https://discuss.elastic.co/u/matled)\
**Post date:** [June 30, 2023, 2:08pm UTC](https://discuss.elastic.co/t/fleet-server-8-8-1-on-prems-boot-issue/337312/4 "2023-06-30T14:08:46Z")

</div>

I'm asking myself the same. I don't know where to increase the timeout. It could be hardcoded in the routine of the fleet integration that is applied to the elastic-agent. This would mean this should be tracked as an official optimization or bug.

Or we have an issue with our setup. 🙂

---

_[View the full topic](https://discuss.elastic.co/t/fleet-server-8-8-1-on-prems-boot-issue/337312)._