I have installed and run ECK 8.7.1 with fleet: $ k get agent NAME HEALTH AVAILABLE EXPECTED VERSION AGE elastic-agent green 6 6 8.7.1 84m fleet-server green 3 3 8.7.1 84m Kibana version: 8.7.1 Elasticsearch version: 8.7.1 …

I'm assuming the issue was the serverUrl wasn't specified and therefore picking up the default, so the new config would look something like the below: var apm = require('elastic-apm-node').start({ // Override service name from package.json // Allowed characters: a-z, A-Z, 0-9, -, _, and space …

ECK Fleet APM Node.JS agent logs "APM Server transport error (ECONNREFUSED): connect ECONNREFUSED 127.0.0.1:8200"

Elastic Observability APM

Kok_How_Teh (Kok How Teh) May 20, 2023, 5:33am 6

Yes, setting serverUrl and verifyServerCert: false is the solution. Thanks.

1 Like

Topic		Replies	Views
"APM Server transport error (ECONNREFUSED): connect ECONNREFUSED ::1:8200" when trying to configure APM agent in application code APM nodejs	9	2902	March 16, 2023
APM Server transport error (ECONNREFUSED): connect ECONNREFUSED 127.0.0.1:8200 APM nodejs , server	4	5354	October 1, 2019
APM Server transport error (ECONNREFUSED) APM nodejs , server	2	1198	January 27, 2023
Elastic APM: Instance rejected connection APM nodejs	3	529	November 9, 2023
APM for AWS Lambda 'APM Server transport error (ECONNREFUSED)' APM	2	1143	March 15, 2019

ECK Fleet APM Node.JS agent logs "APM Server transport error (ECONNREFUSED): connect ECONNREFUSED 127.0.0.1:8200"

Related topics