Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > HTTPS prefix in URL variables for alerts and reports are not populating

HTTPS prefix in URL variables for alerts and reports are not populating

Created by Eric Bryant, last modified by MindTouch on Jun 23, 2016

Views: 95 Votes: 1 Revisions: 4

Overview

This article explains how to troubleshoot or resolve a problem with either returning HTTP value for a URL variable and not the desired prefix of SSL enabled HTTPS in URL link of an alert message or report link. Example variables:

${N=SwisEntity;M=DetailsUrl}.
${N=Alerting;M=AlertDetailsUrl}
 ${N=Alerting;M=AcknowledgeUrl}

Environment

All versions of NPM

 

Cause 

There could be several causes for this issue. Mostly, the websites table as well as the IIS binding should be set for HTTPS only and to be entered and setup properly.

 

Troubleshooting/Resolution Steps

  1. Open IIS on the Orion server:

https://msdn.microsoft.com/en-us/lib.../bb763170.aspx

   2.  Set HTTPS Binding:

https://technet.microsoft.com/en-us/...(v=ws.10).aspx

   3.  Enable SSL in IIS:

https://support.microsoft.com/en-us/kb/324069

or  see the link below:

https://solarwinds-prod.mindtouch.us...on_Web_Console

See the given example below:

 

Note: Make sure that the ServerName field on websites table matches Issue by in Certificate added in IIS if passed through DNS and or redirect setup for FQDN servername or thus matching what the redirect is for the hostname in DNS.

 

  4.  Restart Orion services on All Websites servers.

 

Last modified
22:29, 22 Jun 2016

Tags

Classifications

Public