# OneAgent not detecting Node.js/React web application

**URL:** <https://community.dynatrace.com/t/oneagent-not-detecting-node-js-react-web-application/38349>\
**Category:** Real User Monitoring\
**Tags:** real-user-monitoring-classic, application-monitoring\
**Created:** [February 9, 2023, 9:31am UTC](https://community.dynatrace.com/t/oneagent-not-detecting-node-js-react-web-application/38349 "2023-02-09T09:31:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mdouds](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@mdouds](https://community.dynatrace.com/u/mdouds)\
**Post date:** [February 9, 2023, 4:04pm UTC](https://community.dynatrace.com/t/oneagent-not-detecting-node-js-react-web-application/38349/2 "2023-02-09T16:04:13Z")

</div>

Hi [@cameronduff](https://community.dynatrace.com/user/57062),

There are a number of possible problems. First things I would check:

- Is your web application detection rules configured for the correct URL? Make sure to test your URL in the “Check existing detection rules” section.
- Is there a proxy in front of your web server that manipulates the URL path? We have seen cases where the URL/domain gets changed to a URL that does not find a match in the web detection rules.
- Do you see a “ruxitagent” javascript injected into the \<head\> of your site, but when viewing this javascript request in Fiddler or your browser’s developer tools you see a 404 or another error? By default, this JS path is the root of your site. If needed, you can configure it to load from a specific path in your app settings in Dynatrace under Capturing \> Advanced Setup.

These are the most common issues we’ve seen, but feel free to open a support request; the DT support team is very knowledgeable when it comes to troubleshooting RUM issues.

---

_[View the full topic](https://community.dynatrace.com/t/oneagent-not-detecting-node-js-react-web-application/38349)._
