# No access to APM API **URL:** \ **Category:** APM\ **Tags:** server\ **Created:** [April 13, 2022, 8:51am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307 "2022-04-13T08:51:52Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![dthapostle](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@dthapostle](https://discuss.elastic.co/u/dthapostle)\ **Post date:** [April 13, 2022, 8:51am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/1 "2022-04-13T08:51:52Z")
I **Kibana version** : 7.17.2 **Elasticsearch version** : 7.17.2 **APM Server version** : APM integration 7.17.1 **APM Agent language and version** : [ASP.Net](http://ASP.Net) 7.17.2 **Browser version** : Safari 15.3 **Original install method (e.g. download page, yum, deb, from source, etc.) and version**: deb/apt **Fresh install or upgraded from other version?** fresh installation **Is there anything special in your setup?** ElasticAgent is configured to interact with ES and fleet directly. **Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**: I configured APM integration following the manual located in [APM | Kibana Guide [7.17] | Elastic](https://www.elastic.co/guide/en/kibana/7.17/xpack-apm.html) ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/1/f1fb5c671007123e577dfe07e31c35bd72a195cf.png) I can't access APM API: ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/2/72c0a99a4aa610ba6b2e8107f70d3399a8be80d7.png) **Steps to reproduce** : 1. Install ELK v7.17 2. Install Elastic APM integration following [elastic.co](http://elastic.co) manual 3. Try to access APM API - get 404 **Errors in browser console (if relevant)**: **Provide logs and/or server output (if relevant)**: 22:09:05.916 [elastic\_agent][error] Could not communicate with fleet-server Checking API will retry, error: fail to checkin to fleet-server: Post "[https://elastic3](https://elastic3).\*\*\*:8220/api/fleet/agents/4f590859-53da-4d56-a605-c6bff181389d/checkin?": context canceled 22:09:05.916 [elastic\_agent][error] Could not communicate with fleet-server Checking API will retry, error: fail to checkin to fleet-server: Post "[https://elastic3](https://elastic3).\*\*\*:8220/api/fleet/agents/4f590859-53da-4d56-a605-c6bff181389d/checkin?": context canceled ---
**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\ **Post date:** [April 20, 2022, 9:41am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/2 "2022-04-20T09:41:31Z")
Hi @dthapostle , the [APM Agent Configuration API](https://www.elastic.co/guide/en/kibana/current/agent-config-api.html) is available via the **Kibana** endpoint, not the Fleet Server endpoint. Can you please try with that and let us know if it works. Thanks, Silvia ---
**Author:** ![dthapostle](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@dthapostle](https://discuss.elastic.co/u/dthapostle)\ **Post date:** [April 20, 2022, 10:28am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/3 "2022-04-20T10:28:25Z")
@simitt > [@dthapostle](#): > > agents/4f590859-53da-4d56-a605-c6bff181389d/ Thanks for reply. Using Kibana endpoint I can proceed with agents configurations: [http://logcollect](http://logcollect).\*\*\*\*.com:5601/api/apm/settings/agent-configuration ```auto { "configurations": [ { "service": {}, "settings": {}, "@timestamp": 1649784140647, "applied_by_agent": true, "etag": "05c712546752f5b1fe3b429f84df5d38827a2fdf" } ] } ``` But ASP Test app can't establish connection to config: ![asp_client_apm](https://us1.discourse-cdn.com/elastic/original/3X/9/e/9e6d54a87c0bd5e1d4a03499632d825a4ef857d0.jpeg) ---
**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\ **Post date:** [April 20, 2022, 1:47pm UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/4 "2022-04-20T13:47:40Z")
The apm agent configuration settings can be set and updated directly via Kibana, but are consumed by the APM agents through the APM Server. This way the APM agents do not require a direct connection to Kibana. So for consuming the APM agent configuration, you need to configure the APM Server URL (not the Kibana URL) in the agents. The APM Server URL defaults to port `8200`. ---
**Author:** ![dthapostle](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@dthapostle](https://discuss.elastic.co/u/dthapostle)\ **Post date:** [April 20, 2022, 2:07pm UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/5 "2022-04-20T14:07:54Z")
@simitt thanks. How should I configure it for internal APM server? It seems to ignore apm-server.yml hosted in the same folder: ```auto root@elastic3:/var/lib/elasticsearch# ps ax | grep ap[m] 212053 ? Sl 10:16 /var/lib/elastic-agent/data/elastic-agent-6118f2/install/apm-server-8.1.2-linux-x86_64/apm-server -E management.enabled=true -E gc_percent=${APMSERVER_GOGC:100} -E logging.level=info -E http.enabled=true -E http.host=unix:///var/lib/elastic-agent/data/tmp/default/apm-server/apm-server.sock -E logging.files.path=/var/lib/elastic-agent/data/elastic-agent-6118f2/logs/default -E logging.files.name=apm-server -E logging.files.keepfiles=7 -E logging.files.permission=0640 -E logging.files.interval=1h -E path.data=/var/lib/elastic-agent/data/elastic-agent-6118f2/run/default/apm-server--8.1.2 ``` configuration file: ```auto root@elastic3:/var/lib/elastic-agent/data/elastic-agent-6118f2/install/apm-server-8.1.2-linux-x86_64# grep host apm-server.yml | head -n 5 # Defines the host and port the server is listening on. Use "unix:/path/to.sock" to listen on a unix domain socket. host: "elastic3. **** :8200" # An origin is made of a protocol scheme, host and port, without the url path. # Array of hosts to connect to. # In case you specify and additional path, the scheme is required: `http://localhost:9200/path`. ``` ---
**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\ **Post date:** [April 20, 2022, 3:02pm UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/6 "2022-04-20T15:02:04Z")
The APM agents should not require any specific configuration, the [central config management](https://www.elastic.co/guide/en/apm/agent/dotnet/current/config-core.html#config-central-config) is enabled by default and the apm agent is fetching the information from the configured APM Server URL. The shared screenshot in [No access to APM API - #2 by simitt](https://discuss.elastic.co/t/no-access-to-apm-api/302307/2) suggested that you had the Kibana URL configured in your .NET apm agent. When setting that to the APM Server URL (see this [config example](https://www.elastic.co/guide/en/apm/agent/dotnet/current/configuration-on-asp-net-core.html)), the .NET agent should be good to fetch the information from the APM Server. You shouldn't have to configure anything in the Elastic Agent related to this. When running APM Server managed by Elastic Agent, the APM central configuration settings are automatically passed down from Kibana to the APM Server via the Fleet/Elastic Agent mechanism. So in summary, please ensure that you - use the Kibana path for setting the concrete apm agent central config values - configure the APM Server URL in the .NET apm agent No further config should be required related to this Feature. ---
**Author:** ![dthapostle](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@dthapostle](https://discuss.elastic.co/u/dthapostle)\ **Post date:** [April 20, 2022, 3:32pm UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/7 "2022-04-20T15:32:34Z")
@simitt I have 3 ES nodes: logcollect, elastic2 and elastic3. Elastic agent is installed on elastic3 with ElasticAPM (via Agent policy). There's APM process on elastic3 but it doesn't listen TCP 8200. I can't specify elastic3:8200 in .Net APM agent because built-in APM server on elastic3 doesn't listen TCP 8200: ```auto root@elastic3:~# netstat -ano | grep 82[0,2]0 tcp 0 0 192.168.152.24:45272 192.168.152.24:8220 ESTABLISHED keepalive (8.10/0/0) tcp6 0 0 :::8220 :::* LISTEN off (0.00/0/0) tcp6 0 0 192.168.152.24:8220 192.168.152.24:45272 ESTABLISHED keepalive (8.10/0/0) tcp6 0 0 192.168.152.24:8220 192.168.152.76:59210 ESTABLISHED keepalive (1.79/0/0) root@elastic3:~# ``` ---
**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\ **Post date:** [April 20, 2022, 4:28pm UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/8 "2022-04-20T16:28:35Z")
Please follow the [guide to add the APM Integration](https://www.elastic.co/guide/en/apm/guide/current/apm-quick-start.html#add-apm-integration). When running inside a container, also ensure to configure the `host` via the Fleet UI to listen to all interfaces, see this example: ![Screenshot 2022-04-20 at 18.27.34](https://us1.discourse-cdn.com/elastic/original/3X/6/3/63ab27fb34bd8b3d49c9fd7a6dcf47052ff15ff3.png) ---
**Author:** ![dthapostle](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@dthapostle](https://discuss.elastic.co/u/dthapostle)\ **Post date:** [April 20, 2022, 4:50pm UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/9 "2022-04-20T16:50:26Z")
@simitt I specified for fleet and client policies: ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/3/b3c4a3dde8566342d186c0a43d077d325f6c4b0e.png) and restarted the agent - nobody listens TCP 8200: ```auto root@elastic3:~# service elastic-agent restart root@elastic3:~# netstat -anpo | grep 82[0,2]0 tcp 0 0 192.168.152.24:47960 192.168.152.24:8220 ESTABLISHED 411726/elastic-agen keepalive (2.86/0/0) tcp6 0 0 :::8220 :::* LISTEN 411753/fleet-server off (0.00/0/0) tcp6 0 0 192.168.152.24:8220 192.168.152.76:60600 ESTABLISHED 411753/fleet-server keepalive (10.05/0/0) tcp6 0 0 192.168.152.24:8220 192.168.152.24:47960 ESTABLISHED 411753/fleet-server keepalive (2.86/0/0) root@elastic3:~# ps ax | grep ap[m] 411767 ? Sl 0:00 /var/lib/elastic-agent/data/elastic-agent-6118f2/install/apm-server-8.1.2-linux-x86_64/apm-server -E management.enabled=true -E gc_percent=${APMSERVER_GOGC:100} -E logging.level=info -E http.enabled=true -E http.host=unix:///var/lib/elastic-agent/data/tmp/default/apm-server/apm-server.sock -E logging.files.path=/var/lib/elastic-agent/data/elastic-agent-6118f2/logs/default -E logging.files.name=apm-server -E logging.files.keepfiles=7 -E logging.files.permission=0640 -E logging.files.interval=1h -E path.data=/var/lib/elastic-agent/data/elastic-agent-6118f2/run/default/apm-server--8.1.2 root@elastic3:~# ``` ---
**Author:** ![dthapostle](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@dthapostle](https://discuss.elastic.co/u/dthapostle)\ **Post date:** [April 22, 2022, 6:06am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/10 "2022-04-22T06:06:32Z")
@simitt Could you continue your assistance? ---
**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\ **Post date:** [April 26, 2022, 2:42am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/11 "2022-04-26T02:42:35Z")
What do you get when you ran netstat on the process ID of the APM-server (411767 in your example)? ---
**Author:** ![dthapostle](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@dthapostle](https://discuss.elastic.co/u/dthapostle)\ **Post date:** [April 26, 2022, 6:43am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/12 "2022-04-26T06:43:59Z")
Hi @xeraa. ```auto root@elastic3:/home/aleksey# ps ax | grep ap[m] 412657 ? Sl 26:30 /var/lib/elastic-agent/data/elastic-agent-6118f2/install/apm-server-8.1.2-linux-x86_64/apm-server -E management.enabled=true -E gc_percent=${APMSERVER_GOGC:100} -E logging.level=info -E http.enabled=true -E http.host=unix:///var/lib/elastic-agent/data/tmp/default/apm-server/apm-server.sock -E logging.files.path=/var/lib/elastic-agent/data/elastic-agent-6118f2/logs/default -E logging.files.name=apm-server -E logging.files.keepfiles=7 -E logging.files.permission=0640 -E logging.files.interval=1h -E path.data=/var/lib/elastic-agent/data/elastic-agent-6118f2/run/default/apm-server--8.1.2 root@elastic3:/home/aleksey# netstat -anop | grep 412657 tcp 0 0 127.0.0.1:36322 127.0.0.1:6789 ESTABLISHED 412657/apm-server keepalive (10.46/0/0) unix 2 [ACC] STREAM LISTENING 962546 412657/apm-server /var/lib/elastic-agent/data/tmp/default/apm-server/apm-server.sock unix 3 [] STREAM CONNECTED 969762 412657/apm-server /var/lib/elastic-agent/data/tmp/default/apm-server/apm-server.sock unix 3 [] STREAM CONNECTED 969766 412657/apm-server /var/lib/elastic-agent/data/tmp/default/apm-server/apm-server.sock unix 3 [] STREAM CONNECTED 969764 412657/apm-server /var/lib/elastic-agent/data/tmp/default/apm-server/apm-server.sock root@elastic3:/home/aleksey# ``` ---
**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\ **Post date:** [April 26, 2022, 12:57pm UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/13 "2022-04-26T12:57:44Z")
Can you spot anything helpful in the Elastic Agent or APM Server logs? You should be able to [view them via Kibana](https://www.elastic.co/guide/en/fleet/current/elastic-agent-logging.html) or access them directly from the `elastic3` container (see the [default logging parameters](https://www.elastic.co/guide/en/fleet/current/elastic-agent-standalone-logging-config.html)). ---
**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\ **Post date:** [April 27, 2022, 2:05am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/14 "2022-04-27T02:05:59Z")
I don't have that on-prem setup running right now to check, but I'm surprised the only `LISTENING` is a unix socket (for the HTTP metrics) but nothing on port 8200 (or whatever you have configured) — unless that's what you'd expect, Silvia? Otherwise the logs might be interesting around what this is binding to. ---
**Author:** ![dthapostle](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@dthapostle](https://discuss.elastic.co/u/dthapostle)\ **Post date:** [April 27, 2022, 7:42am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/15 "2022-04-27T07:42:49Z")
@simitt @xeraa I uploaded logs to [OneDrive](https://1drv.ms/u/s!AvI0FfKmTXQ7j8l5dxxqpo-eF1y38A?e=5xv4PG) ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/2/22876f197b449a82ea736a455aa8885342b05bac.png) ---
**Author:** ![dthapostle](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@dthapostle](https://discuss.elastic.co/u/dthapostle)\ **Post date:** [May 2, 2022, 11:06am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/16 "2022-05-02T11:06:06Z")
@simitt @xeraa any ideas? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 23, 2022, 7:07am UTC](https://discuss.elastic.co/t/no-access-to-apm-api/302307/17 "2022-05-23T07:07:05Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.