# See what endpoint APM is using - 404 error

**URL:** <https://discuss.elastic.co/t/see-what-endpoint-apm-is-using-404-error/248040>\
**Category:** APM\
**Tags:** nodejs\
**Created:** [September 9, 2020, 4:13pm UTC](https://discuss.elastic.co/t/see-what-endpoint-apm-is-using-404-error/248040 "2020-09-09T16:13:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jdel\_snaps](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jdel_snaps/32/75315_2.png) [@jdel\_snaps](https://discuss.elastic.co/u/jdel_snaps)\
**Post date:** [September 9, 2020, 4:13pm UTC](https://discuss.elastic.co/t/see-what-endpoint-apm-is-using-404-error/248040/1 "2020-09-09T16:13:05Z")

</div>

I'm using the latest version of the Nodejs APM agent (3.7.0) and running against a trial install of Elastic APM hosted on Elastic. I've configured the agent using both inline configuation (apm.start({})) and environment variables, but I keep getting 404 errors when APM tries to connect.

I'm not sure why this is happening, but I can't tell what URL the APM agent is trying to connect to. I copied the configuration exactly as it appeared in the tutorial. Is there any way to see what endpoint the APM agent is trying to connect to?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 30, 2020, 12:13pm UTC](https://discuss.elastic.co/t/see-what-endpoint-apm-is-using-404-error/248040/2 "2020-09-30T12:13:23Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.