Potential Impact to OneAgent Customers Running nginx on Red Hat

Update timeline

1. identified Jul 02, 2026, 11:58 AM UTC

   We have identified an issue affecting customers running nginx with Dynatrace OneAgent in specific Red Hat environments, where requests may return HTTP 500 responses. The issue is limited to certain Red Hat nginx package versions and configurations, and may result in failures for all requests handled by impacted nginx instances. Affected nginx versions include 1.20 (latest RHEL 9.8 package), 1.24, and 1.26. Our teams are actively working on mitigation and evaluating available workaround options. For more details on affected configurations and available workarounds, please refer to our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Red-Hat-NGINX-package-introduces-a-regression-with-OneAgent/ta-p/301487 We will continue to provide updates on this page as more information becomes available. We apologize for the inconvenience.

2. identified Jul 02, 2026, 07:45 PM UTC

   We are actively working to resolve an issue that may affect customers using nginx with Dynatrace OneAgent in certain Red Hat environments. In some cases, this may result in HTTP 500 responses. Our teams are deploying a fix to address the issue and are continuing work toward full mitigation. Customers who are still experiencing impact can refer to our Community post for additional details about affected configurations and available workarounds: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Red-Hat-NGINX-package-introduces-a-regression-with-OneAgent/ta-p/301487 We apologize for any inconvenience and appreciate your patience as we work to fully resolve this issue.

3. identified Jul 03, 2026, 09:05 AM UTC

   We are actively working to resolve an issue affecting customers using nginx with Dynatrace OneAgent in certain Red Hat environments, which may result in HTTP 500 responses. As a mitigation, customers can upgrade to OneAgent version 1.339.70 or later, which prevents application from returning HTTP 500 responses. However, the lack of tracing still persists on those affected versions. The underlying issue in certain nginx packages provided by Red Hat still exists. We are actively working with Red Hat and continuing efforts toward a permanent resolution. For more details on affected configurations and available workarounds, please refer to our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Red-Hat-NGINX-package-introduces-a-regression-with-OneAgent/ta-p/301487 We will continue to provide updates on this page as more information becomes available. We apologize for the inconvenience

4. identified Jul 03, 2026, 02:06 PM UTC

   We have identified an additional workaround that can restore tracing functionality in affected environments. Details, implementation instructions, and validation information have been added to the Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Red-Hat-nginx-package-introduces-a-regression-with-OneAgent/ta-p/301487 We continue to work with Red Hat and will provide further updates as more information becomes available.