Anomaly Detection not working in 2026.1.1 version

Question

a {

text-decoration: none;

color: #464feb;

}

tr th, tr td {

border: 1px solid #e6e6e6;

}

tr th {

background-color: #f5f5f5;

}

Copilot said:

I'm running SolarWinds Observability Self-Hosted Advanced 2026.1.1 with Platform Connect healthy (Registered, Connected, and OTEL Accessible), but the anomaly-detection plugin shows a failed status. The UAMS logs report TLS handshake timeout while downloading metadata from https://agent-plugins.cloud.solarwinds.com/rstuf/2.root.json; however, DNS resolution, Test-NetConnection on port 443, and a manual curl request all succeed, with curl returning HTTP 404 (NoSuchKey for rstuf/2.root.json). Has anyone encountered this issue or knows if this is a known UAMS/plugin repository problem in 2026.1.1?

swaminathan26_ · Answer

Hi PJC ,

Thanks for taking your time and replied to my query , the thing is everything is in place for us , and we did performed the steps provided by you , but still it throws the same error.

My another query is , is it expected where this anomaly detection not working in 2026.1.1 version? anyone faced this issue earlier ?

PJC · Answer

Thanks for including the logs. I’d treat this as an endpoint connectivity issue first, rather than an anomaly-detection configuration problem. The key error is the repeated TLS handshake timeout while UAMS is trying to reach agent-plugins.cloud.solarwinds.com; the 404 returned for the specific 2.root.json probe does not, by itself, show that the repository is unavailable.

Please verify outbound TCP 443 from the main polling engine, including any proxy or TLS inspection policy, and make sure agent-plugins.cloud.solarwinds.com is allow-listed and trusted by the account running UAMS. After correcting that, restart the UAMS Client and recheck the anomaly-detection plugin. If it remains critical, run the UAMS diagnostics and attach the resulting logs to a Support case.