Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Connection attempt failed! Unknown error during F5 iControl test

Connection attempt failed! Unknown error during F5 iControl test

Updated September 21, 2017


When trying to add F5 credentials in the Orion Web Console, you get the following error:

Connection attempt failed! Unknown error during F5 iControl test
WARN  SolarWinds.F5.Pollers.API.F5ApiClient - 
Test connection failed for https://"F5 IP Address" 
Error: Solarwinds.F5.Common.Models.API.F5ApiException: Unknown error during F5 iControl 
   at SolarWinds.F5.Pollers.API.F5ApiClient.Execute(RestApiRequest request)
   at SolarWinds.F5.Pollers.API.F5ApiClient.GetData(String path)
   at SolarWinds.F5.Pollers.API.F5ApiClient.TestConnection().
   ERROR SolarWinds.F5.Pollers.API.F5ApiClient - Invalid response from https://"F5 IP Address"/:
    Status=0, Content=, ErrorMessage=Error executing HTTP Web Request. 
   URL: https://"F5 IP Address"/mgmt/tm/ltm/, ErrorException=System.Net.WebException: 
   The request was aborted: Could not create SSL/TLS secure channel.


  • NPM versions 12 and above


The F5 SSL certificate is an MD5 certificate, and the Microsoft .NET version on the Orion Server is 4.6 or later.


Microsoft .NET Framework 4.6 adds TLS 1.2, and TLS 1.2 does not support MD5 certificate authentication.


The .NET Framework 4.6 adds TLS 1.1 and TLS 1.2 to the WCF SSL protocol default list.


For more info please see this Microsoft Post (©03/30/2017 Microsoft, available at, obtained on 22/09/2017).


  1. From the Orion Server, browse to the F5 API using Internet Explorer.
  2. When the page loads, select the padlock icon from the browser address bar and select view certificate.



view certs.png

  1. Go to the details tab.
  2. Check the signature hash algorithm.
  3. If it is MD5, then the issue is that the certificate is not supported by .NET 4.6.
  4. To check the .NET version, please see the following Microsoft support doc (©08/09/2017 Microsoft, available at, obtained on 22/09/2017).
  5. If the certificate is MD5, please contact F5 to have this upgraded to a supported certificate or revert to .NET 4.5


Last modified