Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Redirect the SolarWinds website from HTTP to HTTPS in Windows 2012 R2

Redirect the SolarWinds website from HTTP to HTTPS in Windows 2012 R2

Table of contents

Updated April 12th, 2016

Overview

This article provides steps on how to redirect the SolarWinds website from HTTP to HTTPS in Windows 2012 R2.

Environment

All Core Products

Steps

  1. Log in to the Orion Server, click Start then open the Server Manager.
  2. On the upper right hand, click Manage > Add Roles and Features.
  3. Click Next until you reach the Server Roles.
  4. Expand Web Server (IIS) > Web Server > Common HTTP Features > Tick HTTP Redirection.
  5. Click Install on the Confirmation window.
  6. Click Close on the Results window
  7. Add the HTTPS 443 in Port Bindings:
    1. Open Internet Information Services (IIS).
    2. Expand the Server > Sites > Select SolarWinds NetPerfMon.
    3. On the right window pane select Bindings under Actions then click Add.
    4. In Port, enter 443.
    5. In SSL certificate, enter SolarWinds-Orion.
    6. Click OK.
  8. Redirect from HTTP to HTTPS (If required). Use Default IIS Website. Create your own if this is not visible. To do this:
    1. Right-click Sites.
    2. Select Add Web Site.  
    3. Note: You can create a new website with your preferred path and name. 
  9. Once the website has been added, right-click Default Website, and select click HTTP Redirect.

 

Note: You have an option to select your destination in the Redirect request to this destination.

https://192.168.168.222

https://myorionservername

https://npm.mydomain.com

 

 

Every request to access Port HTTP 80 should now be redirected to Port 443 HTTP.

Last modified

Tags

Classifications

Public