Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > HTTP 404 Not found when accessing the website using the hostname

HTTP 404 Not found when accessing the website using the hostname

Created by Malik Haider, last modified by Daniel Polaske on Jun 15, 2017

Views: 4,934 Votes: 3 Revisions: 9


This article addresses the issue where the Orion website is inaccessible using the hostname even when it is accessible using the IP address and the following error:

HTTP 404 Not found



NPM 11.0 and later


This can occur when proxy redirection is configured within Internet Explorer.


Settings > 


Connections > LAN settings > 



1.  Remove the Proxy settings from Internet Explorer. 

Screenshots property of © 2016 Microsoft.

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.


2.  If the above resolution does not help, please also refer to the following article which describes general bindings and DNS resolution issues which can also be a factor in receiving a 404 error:


Orion Web Console gives an HTTP Error 404


Last modified