Release Notes 2.0.1

These release notes contain information about new features, improvements, and known issues in NGINX Instance Manager.

We recommend installing the latest version of NGINX Instance Manager to take advantage of the newest features and updates.




January 27, 2022

Resolved Issues

This release includes the following fixes. To view the history and details for an issue, search the NGINX Docs for the issue ID.

  • Unable to access the NGINX Instance Manager web interface after loading SELinux policy (31583)

  • The nms-dpm service restarts when registering multiple NGINX Agents with the same identity (31612)




Known Issues

The following issues are known to be present in this release. Look for updates to these issues in future release notes.

  • gRPC errors occur when starting NGINX Instance Manager (28683)

    When starting NGINX Instance Manager, you may see errors similar to the following in /etc/nginx/conf.d/nms-http.conf:227:

    nginx[1234]: nginx: [emerg] unknown directive "grpc_socket_keepalive"
    

    Workaround:

    Make sure your version of NGINX is v1.18 or later. See the Technical Specifications guide for details.

  • NGINX/NGINX Plus is not a requirement when installing NGINX Instance Manager on CentOS 7, RHEL 7, and Amazon Linux 2 (28758)

    When installing on CentOS 7, RHEL 7, and Amazon Linux 2, the package manager doesn’t prevent installing NGINX Instance Manager with unsupported versions of NGINX or NGINX Plus. As a consequence, it is possible that nms-instance-manager is installed without an NGINX gateway. Resulting in a less than optimal experience.

    Workaround:

    Install a supported version of NGINX (v1.18 or later) or NGINX Plus (R22 or later). See the Technical Specifications guide for details.

  • Include cycles in the configuration cause analyzer to spin. (31025)

    A configuration containing a cycle will cause the analyzer to timeout before causing an nms-dpm restart.

    nginx.conf:
    http {
    include conf.d/server-1.conf
    }
    conf.d/server-1.conf:
    server {
    listen 80;
    include conf.d/server-2.conf
    }
    
    conf.d/server-2.conf
    server {
    listen 443;
    include conf.d/server-1.conf
    }
    

    Workaround:

    Avoid uploading configurations that contain cycles.

  • The web interface doesn’t report an error when uploading config files larger than 50 MB (31081)

    In the web interface, when uploading a config file that’s larger than 50 MB (max size), the system incorrectly reports the state as Analyzing (Status code 403), although the upload failed.

    Workaround:

    Keep config files under 50 MB.

  • System reports “error granting scope: forbidden” if user granting permissions belongs to more than one role (31215)

    If a user is assigned to multiple roles for Instance Management and Settings, and the user has WRITE access for Settings, which allows for creating new roles, the user cannot grant permissions to new roles or existing ones. The system returns an error similar to the following: “Error granting scope: forbidden. You cannot grant access for a scope you are not assigned to.”

    Workaround:

    Combine all permissions into one role for the user, allowing them to create new roles with the same set of permissions.

  • After upgrading NGINX, NGINX Instance Manager reports the old NGINX version (31225)

    After upgrading NGINX to a new version, the NGINX Instance Manager web interface and API report the old NGINX version until the NGINX Agent is restarted.

    Workaround:

    Restart the Agent to have the new version reflected properly:

    systemctl restart nginx-agent
    
  • When using Instance Groups, tag-based access controls are not enforced (31267)

    When using the experimental Instance Groups feature, access controls based on instance tags are not enforced. We recommend only using Instance Groups at this time if you are not relying on tag-based access controls.

  • Bad Gateway (502) errors with Red Hat 7 (31277)

    On RHEL 7, when authenticating with basic auth, the web interface may become unresponsive and return a 502 error.

    Workaround:

    1. Verify that NGINX is added to the NMS group:

      id nginx
      

      The expected output looks similar to the following example:

      uid=994(nginx) gid=991(nginx) groups=991(nginx),992(nms)
      
    2. If the NMS group is missing, run the following command to add it:

      usermod -a -G nms nginx
      
    3. Restart each daemon:

      systemctl start nms-core
      systemctl start nms-dpm
      systemctl start nms-ingestion
      
  • Unable to register multiple NGINX Agents in containers on the same host (30780)

    NGINX Instance Manager v2.0 does not support containers at this time. Look for support in a future release.




Supported Versions