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 > Network Performance Monitor (NPM) > Report scheduled job fails via HTTPS

Report scheduled job fails via HTTPS

Created by Adrian Cook, last modified by Aileen de Lara_ret on Jun 28, 2016

Views: 1,023 Votes: 3 Revisions: 8


This article provides brief information and steps to resolve the issue when report jobs fail using a website on HTTPS.


All Orion Core products



Any of the following cause the issue:

  • A wrong or expired certificate for the Solarwinds web site in IIS.
  • A certificate is set to FQDN but the URL used for the report website is the hostname.
  • The website is set on an IP address only and not 'all unassigned'.
  • HTTPS is not correctly setup in IIS and the Websites table.


Change the HTTPS to HTTP. If the report job still fails, do the following steps: 

1. Go to IIS Manager.

2. Click Sites.

3. Right-click SolarWinds website, and select Edit Bindings. 

4. Click HTTPS Binding and click Edit. 

View the certificate and make sure that it is issued to the correct server and if so it is using the hostname or the FQDN and update the URL on the report to use what the certificate is issued to. If they are not using a URL in the report but are pointing to a existing report you can update the Websites table in the database to use the FQDN instead of the hostname for the web site.

5. If the certificate has expired, create a new self-signed certificate or get a new certificate from the certificate authority.


If changing the HTTPS to HTTP corrects the issue then this may be due to an incorrectly configured HTTPS, please do the following:

1. Go to Orion Database Manager.

2. Select default database.

3. Expand the tables and scroll down to the Websites table, double click this.

4. Enable table editing.

5. Confirm and if the Port is set to 80 change this to 443.

6. Confirm and if the SSL-enabled is set to 0 change this to 1.




Last modified