HTTPS Monitors Fail with Timeouts After Upgrade to SAM 2026.2.1

After upgrading to SolarWinds Platform / SAM 2026.2.1, some HTTPS Monitor components begin failing even though the target sites are healthy.
Impacted monitors typically use Follow Redirect = Follow and hit URLs that perform multiple HTTP redirects (for example, login portals).

A regression in the HTTPS Monitor redirect handling logic in 2026.2.0 / 2026.2.1 causes probes configured with Follow Redirect = Follow to hang when following multi-step HTTP 3xx redirect chains.
After the probe waits for the full timeout period, it incorrectly reports the request as failed (HTTP 408 / timeout), even though the endpoint is reachable and responds correctly when tested outside SolarWinds.

Workaround

Until the fixed version is installed, use the following workaround on affected HTTPS Monitors:

1. Edit the impacted HTTPS Monitor component.
2. Set Follow Redirect to No.
3. Where possible, update the URL to point directly to the final destination page (post-redirect) instead of the initial URL.
4. Save the changes and re-test the component.

This restores correct polling and availability reporting, though it may not fully exercise the complete redirect or login flow.

Resolution

• The issue is fixed in SolarWinds Platform / SAM version 2026.2.2.
• If you experience this behavior in 2026.2.0 / 2026.2.1:
  • Apply the Follow Redirect = No workaround as a temporary measure, and
  • Plan an upgrade to 2026.2.2 or later during the next suitable maintenance window to obtain the permanent fix and then re-enable Follow Redirect = Follow where required.