Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Error after upgrading to NPM 12.0.1: The server committed a protocol violationSection=responsestatusline

Error after upgrading to NPM 12.0.1: The server committed a protocol violationSection=responsestatusline

Updated November 22, 2016

Overview

While configuring proxy settings after upgrading to NPM 12.0.1 and using a cloud proxy server called WebDefence, the following error displays after entering proxy settings and authentication details:

The server committed a protocol violationSection=responsestatusline

There are no errors in the Orionweb.log related to proxy.

Environment

NPM 12.0.1

Resolution

The work around is to add the following URIs in the white list in cloud proxy interface:

  • *.solarwinds.com
  • *.solarwinds.com:443

Adding these to the white list will not require any authentication (if authentication by pass is enabled on the cloud proxy end).

Note: This work around is recommended by Cloud Proxy.

 

 

Last modified

Tags

Classifications

Public