# OneAgent (cloudNativeFullStack) fails to install when proxy username contains a domain backslash (DOMAIN\\user)

**URL:** <https://community.dynatrace.com/t/oneagent-cloudnativefullstack-fails-to-install-when-proxy-username-contains-a-domain-backslash-domain-user/57224>\
**Category:** Container platforms\
**Tags:** openshift, kubernetes\
**Created:** [October 26, 2026, 4:02pm UTC](https://community.dynatrace.com/t/oneagent-cloudnativefullstack-fails-to-install-when-proxy-username-contains-a-domain-backslash-domain-user/57224 "2026-10-26T16:02:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![miguel\_balsa](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/miguel_balsa/32/10427_2.png) [@miguel\_balsa](https://community.dynatrace.com/u/miguel_balsa)\
**Post date:** [October 26, 2026, 4:02pm UTC](https://community.dynatrace.com/t/oneagent-cloudnativefullstack-fails-to-install-when-proxy-username-contains-a-domain-backslash-domain-user/57224/1 "2026-10-26T16:02:13Z")

</div>

I’m deploying Dynatrace on OpenShift with Dynatrace Operator v1.10.2 (DynaKube `v1beta6`, `cloudNativeFullStack`). Outbound traffic must go through an authenticated corporate proxy, and the proxy username includes a Windows domain (`DOMAIN\user`).

The proxy is configured via `spec.proxy.valueFrom`, pointing to a Secret with the key `proxy`. Following the docs, the backslash is URL-encoded:

```auto
http://DOMAIN%5Cuser:<password>@<proxy-host>:<port>

```

With this Secret, everything works except the OneAgent: the Operator reaches the tenant, the images are pulled, and the ActiveGate connects through the proxy without issues.

The OneAgent pods, however, never become Ready and restart in a loop. The readiness probe fails with:

```auto
Cannot find /opt/dynatrace/oneagent/agent/conf/watchdog.conf

```

The container log shows the installer stopping right after loading the proxy configuration:

```auto
Attempting to load proxy host from /var/lib/dynatrace/secrets/internal-proxy/host
Setting proxy host: DOMAIN\user:REDACTED@<proxy-host>:<port>
...
awk: cmd. line:47: warning: regexp escape sequence `\F' is not a known regexp operator

```

It looks like the `%5C` gets decoded into a literal backslash, and the installer then uses the value inside an `awk` regex, where `\` plus the first letter of the username is treated as an escape sequence.

Things I’ve already checked:

- Since Operator 1.3.0, the OneAgent → in-cluster ActiveGate connection bypasses the proxy by default, so the OneAgent doesn’t actually need the proxy in this setup.
- `feature.dynatrace.com/oneagent-ignore-proxy` is deprecated in favor of `feature.dynatrace.com/no-proxy`.
- `no-proxy` doesn’t seem to help: it only excludes destinations, but the proxy string is still passed to the OneAgent, and the installer fails while parsing it before connecting anywhere.

Questions:

1. Is a proxy username containing a domain backslash supported for containerized OneAgent? Is there an encoding that the installer parses correctly?
2. Is this a known issue, and is there a fixed version?
3. Is there a supported way to prevent the proxy configuration from reaching the OneAgent, while keeping it for the Operator and ActiveGate?

Any experience or workarounds would be appreciated. Thanks!
