Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

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 Caroline Juszczak on Nov 03, 2017

Views: 1,743 Votes: 2 Revisions: 5

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

Tags

Classifications

Public