Skip to main content

Access List Issues

Issue:

Implementing an Access List on a Proxy Host results in a '403: Forbidden' message rather than bringing up the basic authentication pop-up window. 

 Access List may have worked correctly previously, but any change made and saved to the proxy host, even unrelated changes, breaks the access list functionality.

Version(s) Affected: 2.12.1

This problem has appeared off and on in various previous versions to the version outlined here.

Cause & Solution:

NPM is removing the authentication header in the NGINX configuration when the proxy host is modified and saved. This breaks authentication. 

As a workaround, you will will have to:

  1. Manually add proxy_set_header Authorization ""; inside the location block in the NGINX configuration file.
  2. Restart the NGINX service to apply the changes.

Back to top