You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NGINX Instance Manager 2.21.0 supports upgrades from these previous versions:
25
25
26
-
- 2.18.0 - 2.20.0
26
+
- 2.18.0 - 2.20.1
27
27
28
28
If your NGINX Instance Manager version is older, you may need to upgrade to an intermediate version before upgrading to the target version.
29
29
@@ -34,13 +34,13 @@ This release includes the following updates:
34
34
- {{% icon-feature %}} **Expanded options for configuring security policies with F5 WAF for NGINX**<aname="2-21-0-whats-new-Expanded-options-for-configuring-security-policies-with-F5-WAF-for-NGINX-45801"></a>
35
35
36
36
You can now configure additional policy settings for F5 WAF for NGINX directly in the NGINX Instance Manager web interface, including:
37
-
37
+
38
38
- Signature sets
39
39
- Signature exceptions
40
40
- Parameters
41
41
- URLs
42
42
- Cookies
43
-
43
+
44
44
For more information, see the [F5 WAF for NGINX Integration Guide](https://docs.nginx.com/nginx-instance-manager/waf-integration/).
45
45
46
46
- {{% icon-feature %}} **Added support for bot signatures management in NGINX Instance Manager**<aname="2-21-0-whats-new-Added-support-for-bot-signatures-management-in-NGINX-Instance-Manager-45827"></a>
@@ -90,21 +90,21 @@ This release includes the following updates:
90
90
- {{% icon-feature %}} **On-demand WAF policy compilation (bundle creation) in NGINX Instance Manager web interface**<aname="2-21-0-whats-new-On-demand-WAF-policy-compilation-(bundle-creation)-in-NGINX-Instance-Manager-web-interface-46672"></a>
91
91
92
92
This release adds on-demand compilation of WAF policies in the NGINX Instance Manager web interface. Pre-compiling policies helps reduce publish times and improve reliability.
93
-
93
+
94
94
Previously, NGINX Instance Manager reused compiled bundles when available and compiled policies during publish if no bundle existed. This could slow down or occasionally fail. You can now compile policies in advance so they’re ready for immediate deployment to instances or instance groups.
95
-
95
+
96
96
**What’s new**
97
-
97
+
98
98
-**Web interface support for policy compilation:** Under **WAF > Policies**, select a policy and choose **Compile (bundle creation)** to start compilation on demand.
99
99
-**Compilation status visibility:** A new **Compilation Status** column shows which policies are already compiled and which need compilation.
100
100
-**Faster publishing:** When a compiled bundle exists for a selected policy, NGINX Instance Manager uses it to speed up publishing to instances and instance groups.
101
-
101
+
102
102
**Upgrade and compatibility**
103
-
103
+
104
104
- No breaking changes. Existing workflows continue to function as before. On-demand compilation through the web interface complements the existing API and can improve publish speed and reduce failures during WAF policy deployment.
105
-
105
+
106
106
**Limitations**
107
-
107
+
108
108
- By default, the **Compile** action uses the latest revision of the selected policy, the most recent compiler version, and the newest versions of attack signatures, bot signatures, and threat campaigns.
109
109
110
110
### Resolved issues {#2-21-0-resolved-issues}
@@ -117,6 +117,36 @@ This release fixes the following issues. Check the [Known Issues]({{< ref "/nim/
117
117
118
118
You can find information about known issues in the [Known Issues]({{< ref "/nim/releases/known-issues.md" >}}) topic.
119
119
120
+
## 2.20.1
121
+
122
+
December 18, 2025
123
+
124
+
### Upgrade Paths {#2-20-1-upgrade-paths}
125
+
126
+
NGINX Instance Manager 2.20.1 supports upgrades from these previous versions:
127
+
128
+
- 2.17.0 - 2.20.0
129
+
130
+
If your NGINX Instance Manager version is older, you may need to upgrade to an intermediate version before upgrading to the target version.
131
+
132
+
### Changes in default behavior{#2-20-1-changes-in-behavior}
133
+
134
+
This release has the following changes in default behavior:
135
+
136
+
- {{% icon-feature %}} **Support for Entrust-CA deprecated**<aname="2-20-1-changes-in-behavior-Support-for-Entrust-CA-deprecated-46910"></a>
137
+
138
+
Entrust CA, used in NGINX Instance Manager licensing flows, will no longer be a trusted certificate authority for browsers. Previous versions of NGINX Instance Manager ship with an embedded licensing bundle that only accepts Entrust-signed certificates for the F5 licensing servers.
139
+
140
+
**The current Entrust certificates used by older NGINX Instance Manager licensing flows will be replaced on February 15, 2026.**
141
+
142
+
To avoid reliance on a single certificate authority, NGINX Instance Manager will trust multiple well-known CAs through an updated certificate bundle. NGINX Instance Manager 2.21 includes this updated bundle so JWT-based licensing and connectivity to the licensing endpoint service continue to work.
143
+
144
+
To prevent service interruptions and provide an extended window for customers to upgrade to version 2.21.0, we are also issuing minor patch releases for versions 2.18.1, 2.19.3, and 2.20.1.
145
+
146
+
### Known issues {#2-20-1-known-issues}
147
+
148
+
You can find information about known issues in the [Known Issues]({{< ref "/nim/releases/known-issues.md" >}}) topic.
149
+
120
150
## 2.20.0
121
151
122
152
June 16, 2025
@@ -125,7 +155,7 @@ June 16, 2025
125
155
126
156
NGINX Instance Manager 2.20.0 supports upgrades from these previous versions:
127
157
128
-
- 2.17.0 - 2.19.2
158
+
- 2.17.0 - 2.19.3
129
159
130
160
If your NGINX Instance Manager version is older, you may need to upgrade to an intermediate version before upgrading to the target version.
131
161
@@ -187,6 +217,36 @@ This release fixes the following issues. Check the [Known Issues]({{< ref "/nim/
187
217
188
218
You can find information about known issues in the [Known Issues]({{< ref "/nim/releases/known-issues.md" >}}) topic.
189
219
220
+
## 2.19.3
221
+
222
+
December 18, 2025
223
+
224
+
### Upgrade Paths {#2-19-3-upgrade-paths}
225
+
226
+
NGINX Instance Manager 2.19.3 supports upgrades from these previous versions:
227
+
228
+
- 2.16.0 - 2.19.2
229
+
230
+
If your NGINX Instance Manager version is older, you may need to upgrade to an intermediate version before upgrading to the target version.
231
+
232
+
### Changes in default behavior{#2-19-3-changes-in-behavior}
233
+
234
+
This release has the following changes in default behavior:
235
+
236
+
- {{% icon-feature %}} **Support for Entrust-CA deprecated**<aname="2-19-3-changes-in-behavior-Support-for-Entrust-CA-deprecated-46909"></a>
237
+
238
+
Entrust CA, used in NGINX Instance Manager licensing flows, will no longer be a trusted certificate authority for browsers. Previous versions of NGINX Instance Manager ship with an embedded licensing bundle that only accepts Entrust-signed certificates for the F5 licensing servers.
239
+
240
+
**The current Entrust certificates used by older NGINX Instance Manager licensing flows will be replaced on February 15, 2026.**
241
+
242
+
To avoid reliance on a single certificate authority, NGINX Instance Manager will trust multiple well-known CAs through an updated certificate bundle. NGINX Instance Manager 2.21 includes this updated bundle so JWT-based licensing and connectivity to the licensing endpoint service continue to work.
243
+
244
+
To prevent service interruptions and provide an extended window for customers to upgrade to version 2.21.0, we are also issuing minor patch releases for versions 2.18.1, 2.19.3, and 2.20.1.
245
+
246
+
### Known issues {#2-19-3-known-issues}
247
+
248
+
You can find information about known issues in the [Known Issues]({{< ref "/nim/releases/known-issues.md" >}}) topic.
249
+
190
250
## 2.19.2
191
251
192
252
May 06, 2025
@@ -250,7 +310,7 @@ February 06, 2025
250
310
251
311
NGINX Instance Manager 2.19.0 supports upgrades from these previous versions:
252
312
253
-
- 2.16.0 - 2.18.0
313
+
- 2.16.0 - 2.18.1
254
314
255
315
If your NGINX Instance Manager version is older, you may need to upgrade to an intermediate version before upgrading to the target version.
256
316
@@ -326,6 +386,36 @@ This release fixes the following issues. Check the [Known Issues]({{< ref "/nim/
326
386
327
387
You can find information about known issues in the [Known Issues]({{< ref "/nim/releases/known-issues.md" >}}) topic.
328
388
389
+
## 2.18.1
390
+
391
+
December 18, 2025
392
+
393
+
### Upgrade Paths {#2-18-1-upgrade-paths}
394
+
395
+
NGINX Instance Manager 2.18.1 supports upgrades from these previous versions:
396
+
397
+
- 2.15.0 - 2.18.0
398
+
399
+
If your NGINX Instance Manager version is older, you may need to upgrade to an intermediate version before upgrading to the target version.
400
+
401
+
### Changes in default behavior{#2-18-1-changes-in-behavior}
402
+
403
+
This release has the following changes in default behavior:
404
+
405
+
- {{% icon-feature %}} **Support for Entrust-CA deprecated**<aname="2-18-1-changes-in-behavior-Support-for-Entrust-CA-deprecated-46907"></a>
406
+
407
+
Entrust CA, used in NGINX Instance Manager licensing flows, will no longer be a trusted certificate authority for browsers. Previous versions of NGINX Instance Manager ship with an embedded licensing bundle that only accepts Entrust-signed certificates for the F5 licensing servers.
408
+
409
+
**The current Entrust certificates used by older NGINX Instance Manager licensing flows will be replaced on February 15, 2026.**
410
+
411
+
To avoid reliance on a single certificate authority, NGINX Instance Manager will trust multiple well-known CAs through an updated certificate bundle. NGINX Instance Manager 2.21 includes this updated bundle so JWT-based licensing and connectivity to the licensing endpoint service continue to work.
412
+
413
+
To prevent service interruptions and provide an extended window for customers to upgrade to version 2.21.0, we are also issuing minor patch releases for versions 2.18.1, 2.19.3, and 2.20.1.
414
+
415
+
### Known issues {#2-18-1-known-issues}
416
+
417
+
You can find information about known issues in the [Known Issues]({{< ref "/nim/releases/known-issues.md" >}}) topic.
0 commit comments