Applications Systems

SAM HTTPS Monitor cannot monitor TLS 1.3–only endpoints in SolarWinds Platform

When using the HTTPS Monitor component in Server & Application Monitor (SAM) to monitor URLs that require TLS 1.3, the component fails with TLS handshake errors.

First published date

2/12/2026 3:21 PM

Last published date

4/9/2026 3:10 PM

Overview

When using the HTTPS Monitor component in Server & Application Monitor (SAM) to monitor URLs that require TLS 1.3, the component fails with TLS handshake errors such as “TLS Security Exception accountable for fallback” and “The request was aborted: Could not create SSL/TLS secure channel.”

This occurs even though the same URL loads successfully in modern web browsers or other TLS 1.3–capable clients.

 

Product section

Server Application Monitor

Cause

This behavior is by design in current releases: the SAM HTTPS Monitor is implemented on .NET HttpWebRequest with a protocol list limited to SSL3, TLS 1.0, TLS 1.1, and TLS 1.2.

It does not currently support TLS 1.3, and cannot successfully negotiate with TLS 1.3–only (or TLS 1.3/PQC-only) endpoints.

 

Resolution

Multiple customer feature requests are tracking this limitation along with a wider platform initiative to add TLS 1.3 support, but as of the latest documented releases there is no native TLS 1.3 support in the SAM HTTPS Monitor and no official ETA.

Recommended options today:

  • If possible, configure the monitored site to offer TLS 1.2 with standard cipher suites so the HTTPS Monitor can connect.
  • If the site must remain TLS 1.3–only, use an alternative/scripted monitor (for example, PowerShell/cURL/Linux script monitors from a TLS 1.3–capable host).

You can raise a new feature request, so it brings more visibility to the engineering team.