Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > ipMonitor > Connection issues with HTTP-based monitors

Connection issues with HTTP-based monitors

Created by Interspire Import, last modified by Karen Valdellon on Jul 05, 2017

Views: 1,460 Votes: 1 Revisions: 9


This article provides information on HTTP-based monitors in ipMonitor and how to troubleshoot connection issues.


All ipMonitor versions


HTTP-based monitors within ipMonitor

  • HTTP: this monitor connects to the “IP Address/Domain Name” specified within the monitor, requests root (“/”), and disconnects.
  • HTML/ASP: this monitor connects to the “IP Address/Domain Name” specified within the monitor, requests the specified “URL”, verifies for a specific string of text within the response, and disconnects.
  • HTTPS: this monitor performs the same function as the HTML/ASP monitor over SSL.
  • HTTP User Experience: this monitor connects to the “IP Address/Domain Name” specified within the Monitor, requests the specified “URL” and calculates a checksum on the file received. All subsequent tests will compare the checksum with the original checksum gathered. If the checksums are different, the monitor will fail. This monitor SHOULD NOT be used for dynamic pages such as ASP and CGI.

Troubleshoot connection issues

  1. Gather the IP Address / Domain Name, TCP port, and URL values from the failing monitor.
  2. On the ipMonitor system, open a CMD window and enter the following command:
    telnet [IP Address/Domain Name] [TCP Port]
  3. When connected to the website, enter the following commands:
    • For the HTTP monitor:
      GET / HTTP/1.0
      Host: [IP Address/Domain Name]
    • For the HTML/ASP monitor and the HTTP User Experience monitor:
      GET /[URL] HTTP/1.0
      Host: [IP Address/Domain Name]

Within the response, make sure that the HTTP status code returned is between 200 and 399. If the monitor is configured to look for text, verify that you can see the searched text within the response.

Another way to troubleshoot connection errors is to use the Debug feature:

  1. Click the monitor name to open the "Edit Monitor" window.
  2. Append "debug" to the end of the URL displayed in the browser, and then press Enter.
     A "debug" button should be displayed in the top gray menu. Click this button and view the communication records between the ipMonitor system and the website.

Install Telnet on Windows

To install Telnet on Windows, see Install Telnet Client (© 2017 Microsoft, available at, obtained on August 15, 2015).


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

Last modified