This document is a summary of the known issues in NGINX Management Suite App Delivery Manager. Fixed issues are removed after 45 days.
We recommend upgrading to the latest version of App Delivery Manager to take advantage of new features, improvements, and bug fixes.
This topic describes an early access feature. These features are provided for you to try before they are generally available. You shouldn't use early access features for production purposes.
Share your thoughts about the documentation by taking this short survey: https://forms.gle/w6eDi53F4UcmDjw68.
The App Delivery Manager module or its pre-configured roles aren’t shown after uploading an App Delivery Manager license.
In a Kubernetes environment, delete the App Delivery Manager pod (which will result in a new pod starting) to resolve this.
In a non-Kubernetes environment, restarting the
nms-admservice will solve this issue:
sudo systemctl restart nms-adm
Template validation can fail for valid templates when trying to publish an environment.
Try publishing the environment again.
Since the built-in templates’ files and directories have been renamed from
yum package manager deletes the older
*builtin* files and all files in the directories with
*builtin* name pattern.
After installing the latest release, access the template directory and manually copy over all the
*builtin* files and directories from the newly created
backup directory to the root of the templates directory.
When the NGINX WAF use case is enabled, a gateway referencing a mix of instance groups with WAF and without WAF goes into an error state if there is a component with WAF enabled referencing another gateway that has an instance group with WAF as a placement.
Do not use gateways that reference instance groups with and without WAF
If a system error on the nginx instance prevents a new configuration from being applied, it can result in App Delivery Manager objects going into an error state when deleted. This prevents the object from being removed from an environment. Multiple attempts to delete the object will also fail.
To remove the object, the instance groups that the object is referencing (direct if a gateway object; indirectly if a component) must temporarily have the instances removed from the instance group.
|42517||Fixed in App Delivery Manager 4.0.0-EA2|
When deploying a configuration with a certificate and key handled by NGINX Management Suite to a custom file path, it may deploy a duplicate copy of the certificate and key to the default /etc/nginx/ path. When deleting the certificate and key, it will only delete the certificate and key in the custom path, leaving the duplicate copy.
Manually delete the certificate and key from the /etc/nginx/ path.
|42429||Fixed in Instance Manager 2.11.0|
It is possible to update an existing certificate’s serial number to one already in use. This incorrectly changes the cert (matching the serial number) details to a new name.
|42425||Fixed in Instance Manager 2.11.0|
Certificate file is not updated automatically when a config change is pushed to an offline instance after it comes back online.
API Documentation is not displaying some description fields for schemas containing references to other objects
API Documentation for Sites, Web Components, and TCP/UDP Components displays the
environmentRef parameter as part of the response in metadata.
environmentRef is not a part of the response of those endpoints.
When the NGINX Agent and NGINX Plus are installed in a container, and the metrics module is also installed on that NGINX Plus instance, any config push to an instance group with that instance will fail.
The stream module requires stream block to be in the config so when loading the metrics module use the stream block as well.
System metrics, as seen in the Overview page, are not displayed for users with roles without elevated access rights, e.g., a Read-only role with no rights to perform other operations like Create, Update, or Delete.
When multiple modules are deployed on the same NGINX Management Suite instance, modules may configure the same server block, and only one config will be applied.
Use Role-based Account Control to prevent sharing of instance groups between App Delivery Manager and API Connectivity Manager.