Release Notes 3.19.2

These release notes contain information about new features, improvements, known issues, and bug fixes in the NGINX Controller API Management Module.

We encourage you to install the latest version of the NGINX Controller APIM module to take advantage of the newest features and updates.

Technical support is provided for earlier versions that were released within two years of the current release.

See Also:

For related installation documentation, refer to the following publications:


Upgrading from NGINX Controller 3.x to NGINX Controller API Management Module 3.18 or later

NGINX Controller 3.x includes the NGINX Controller Application Delivery Module (ADC) and NGINX Controller API Management Module (APIM).

Starting with APIM 3.18, the ADC and APIM Modules are released independently on different schedules.

If you’ve installed NGINX Controller 3.18 or earlier before July 2021, we recommend you use the ADC Module going forward.

However, if you want to upgrade to APIM 3.18 or later, we recommend you upgrade to NGINX Controller 3.17 first.


October 19, 2021

Upgrade Considerations

Take note of the following considerations when upgrading to this version of the NGINX Controller API Management Module:

  • After upgrading NGINX Controller, make sure to upgrade the NGINX Controller Agent too.

  • If you’re upgrading NGINX Controller on a multi-node cluster, run the script on each node individually – the order in which you update the nodes doesn’t matter.

    Never update the control nodes in parallel. Doing so may result in race conditions for certain jobs, such as database migrations, and may cause the cluster to become unavailable.

What’s New

Known Issues

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

  • Managed instances go offline or become unresponsive after registering an NGINX Plus R25 instance with NGINX Controller (33356)

    After an NGINX Plus R25 instance is registered with NGINX Controller, managed instances may appear to go offline or become unresponsive. An error similar to the following is written to the pod/dataplane-manager log:

    panic: runtime error: invalid memory address or nil pointer dereference
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xd2ee26]


    Upgrade to NGINX APIM 3.19.3 or later, or NGINX ADC 3.22 or later

  • Error may be displayed that bd_agent was not found when enabling WAF (29206)

    After installing NGINX App Protect 3.6, the following error message my be displayed when enabling WAF on a component:

    Error: The following module processes were expected but not found: [bd_agent]


    Manually start the bd_agent process on the NAP module using this command: 

    /bin/su -s /bin/bash -c '/opt/app_protect/bin/bd_agent &' nginx.

    Then restart the NGINX service.

  • NGINX service fails to start if SELinux enforcing mode is enabled after NGINX App Protect is deployed (16540)

    Setting SElinux to enforcing mode on an NGINX App Protect Instance may cause the NGINX service to fail to start after the Instance is rebooted.


    Enable SElinux enforcing mode before deploying NGINX App Protect.

Supported NGINX Plus Versions

This version of NGINX Controller works with the following NGINX Plus versions:

  • NGINX Plus R25
  • NGINX Plus R24
  • NGINX Plus R23
  • NGINX Plus R22
  • NGINX Plus R21
  • NGINX Plus R20
  • NGINX Plus R19