# Getting Could not communicate with fleet-server Checking API will retry with elastic agent + Squid proxy + Fleet setup **URL:** \ **Category:** Beats\ **Tags:** docker, fleet, elastic-agent\ **Created:** [June 14, 2022, 8:24am UTC](https://discuss.elastic.co/t/getting-could-not-communicate-with-fleet-server-checking-api-will-retry-with-elastic-agent-squid-proxy-fleet-setup/307113 "2022-06-14T08:24:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Sarvesh\_Sharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sarvesh_sharma/32/98397_2.png) [@Sarvesh\_Sharma](https://discuss.elastic.co/u/Sarvesh_Sharma)\ **Post date:** [June 14, 2022, 8:24am UTC](https://discuss.elastic.co/t/getting-could-not-communicate-with-fleet-server-checking-api-will-retry-with-elastic-agent-squid-proxy-fleet-setup/307113/1 "2022-06-14T08:24:39Z")
We are running elastic agent in our own aws environment which connect to fleet hosted on elastic cloud via a squid proxy. While running the elastic agent, it is able to enroll with fleet successfully but then all of a suddent elastic agent dies with following error: "Could not communicate with fleet-server Checking API will retry, error: fail to checkin to fleet-server: Post "[https://FLEET\_URL:443/api/fleet/agents/c021a75f-e121-467c-9eea-cea250d29bec/checkin](https://FLEET_URL/api/fleet/agents/c021a75f-e121-467c-9eea-cea250d29bec/checkin)?": context canceled" Everything seems fine but not able to find the root cause of the problem ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2022, 4:24am UTC](https://discuss.elastic.co/t/getting-could-not-communicate-with-fleet-server-checking-api-will-retry-with-elastic-agent-squid-proxy-fleet-setup/307113/2 "2022-07-05T04:24:48Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.