# Cannot checking in with fleet-server

**URL:** https://discuss.elastic.co/t/cannot-checking-in-with-fleet-server/374627
**Category:** Elastic Agent
**Tags:** elastic-stack-monitoring
**Created:** [February 17, 2025, 12:43pm UTC](https://discuss.elastic.co/t/cannot-checking-in-with-fleet-server/374627 "2025-02-17T12:43:58Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Viktor\_Movita](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/viktor_movita/32/135707_2.png) [@Viktor\_Movita](https://discuss.elastic.co/u/Viktor_Movita)
#### Post date: [February 17, 2025, 12:43pm UTC](https://discuss.elastic.co/t/cannot-checking-in-with-fleet-server/374627/1 "2025-02-17T12:43:58Z")

</div>

Hello everyone,

For a long time, I was running a Fleet server on a virtual machine.  
Recently, I switched to running the Fleet server in a container using the Elastic image: elastic/elastic-agent.

Intermittently, agents that previously communicated properly are now experiencing communication errors with the Fleet server and switching to Offline status. They occasionally reconnect, but then the issue recurs.  
The log error:

```auto
Cannot checking in with fleet-server, retrying

```

The only error that appears on the Fleet server, I'm not sure if it's related to the case:

```auto
error retrieving resource lock proj/elastic-agent-cluster-leader: leases.coordination.k8s.io "elastic-agent-cluster-leader" is forbidden User: "system:serviceaccount:proj:fleetserver-sa" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "proj"

```

Both setups were running in an **insecure** configuration, using the same ports and firewall settings.

What could be the issue?