Error: fail to communicate with updated API client hosts

[ethical20]

Hi All,

I have a self managed fleet server with one local machine connecting perfectly and i can see logs.

I've installed a new remote cloud machine, the installation was successful but I can't see logs coming.

Checking the remote machine agent logs i can see the following errors:

{"log.level":"info","@timestamp":"2022-09-02T07:51:39.462Z","log.origin":{"file.name":"cmd/run.go","file.line":201},"message":"APM instrumentation disabled","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-09-02T07:51:39.501Z","log.origin":{"file.name":"application/application.go","file.line":78},"message":"Detecting execution mode","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-09-02T07:51:39.538Z","log.origin":{"file.name":"application/application.go","file.line":102},"message":"Agent is managed by Fleet","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-09-02T07:51:39.538Z","log.origin":{"file.name":"capabilities/capabilities.go","file.line":59},"message":"capabilities file not found in C:\\Program Files\\Elastic\\Agent\\capabilities.yml","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-09-02T07:51:40.073Z","log.logger":"composable.providers.docker","log.origin":{"file.name":"docker/docker.go","file.line":44},"message":"Docker provider skipped, unable to connect: protocol not available","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-09-02T07:51:40.118Z","log.logger":"api","log.origin":{"file.name":"api/server.go","file.line":68},"message":"Starting stats endpoint","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-09-02T07:51:40.118Z","log.origin":{"file.name":"application/managed_mode.go","file.line":315},"message":"Agent is starting","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-09-02T07:51:40.118Z","log.logger":"api","log.origin":{"file.name":"api/server.go","file.line":70},"message":"Metrics endpoint listening on: \\\\.\\pipe\\elastic-agent (configured: npipe:///elastic-agent)","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2022-09-02T07:51:56.906Z","log.origin":{"file.name":"fleet/fleet_gateway.go","file.line":208},"message":"failed to dispatch actions, error: fail to communicate with updated API client hosts: Get \"https://192.168.0.3:8220/api/status?\": context deadline exceeded","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2022-09-02T07:51:56.906Z","log.origin":{"file.name":"status/reporter.go","file.line":236},"message":"Elastic Agent status changed to: 'error'","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2022-09-02T07:52:14.189Z","log.origin":{"file.name":"fleet/fleet_gateway.go","file.line":208},"message":"failed to dispatch actions, error: fail to communicate with updated API client hosts: Get \"https://192.168.0.3:8220/api/status?\": context deadline exceeded","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2022-09-02T07:52:31.382Z","log.origin":{"file.name":"fleet/fleet_gateway.go","file.line":208},"message":"failed to dispatch actions, error: fail to communicate with updated API client hosts: Get \"https://192.168.0.3:8220/api/status?\": context deadline exceeded","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2022-09-02T07:52:48.908Z","log.origin":{"file.name":"fleet/fleet_gateway.go","file.line":208},"message":"failed to dispatch actions, error: fail to communicate with updated API client hosts: Get \"https://192.168.0.3:8220/api/status?\": context deadline exceeded","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2022-09-02T07:53:06.524Z","log.origin":{"file.name":"fleet/fleet_gateway.go","file.line":208},"message":"failed to dispatch actions, error: fail to communicate with updated API client hosts: Get \"https://192.168.0.3:8220/api/status?\": context deadline exceeded","ecs.version":"1.6.0"}

Where 192.168.0.3:8220 is the ip of my fleet server.

Any help in this?

[mtojek (Marcin Tojek)]

I would leave it for a few minutes to check if it resolves eventually. Let us know if it helped.

[ethical20]

Hi,

Thanks for your reply, actually ive solved this by adding the ip of the proxy server in the hosts field in fleet settings.

Thanks