Skip to content

Commit cce41c8

Browse files
JTorreGJTorreG
authored
Merge pull request #207 from nginx/internal/nim-release-2.0-kis
Add Nim 2.20 Known issues
2 parents e3af284 + 419266d commit cce41c8

File tree

1 file changed

+81
-83
lines changed

1 file changed

+81
-83
lines changed

‎content/nim/releases/known-issues.md

Lines changed: 81 additions & 83 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,83 @@ This document lists and describes the known issues and possible workarounds in F
1313

1414
---
1515

16+
## 2.20.0
17+
18+
June 16, 2025
19+
20+
### {{% icon-bug %}} Failing to fetch CVE data when using forward proxy in K8s environments {#46177}
21+
22+
{{<bootstrap-table "table table-striped table-bordered">}}
23+
| Issue ID | Status |
24+
|----------------|--------|
25+
| 46177 | Open |
26+
{{</bootstrap-table>}}
27+
28+
#### Description
29+
30+
Fetching latest CVE data from internet might fail if you enable "ssl_verify" in Kubernetes environments.
31+
32+
33+
#### Workaround
34+
35+
1. Switch to the offline CVE database. To switch add the property "offline_nginx_cve: true" under the DPM section in the "nms.conf" file.
36+
37+
```cfg
38+
dpm:
39+
offline_nginx_cve: true
40+
```
41+
42+
2. Download the latest security advisories file from the [nginx.org repository]( https://raw.githubusercontent.com/nginx/nginx.org/main/xml/en/security_advisories.xml) and save them with "cve.xml" as filename in "/usr/share/nms/cve.xml”
43+
3. Restart the `nms` service.
44+
45+
```shell
46+
sudo systemctl restart nms
47+
```
48+
49+
After the restart you will see the line “loading CVE data from file” in the "nms.log" file.
50+
51+
---
52+
53+
### {{% icon-bug %}} New warning message when no usage data or report is available {#46022}
54+
55+
{{<bootstrap-table "table table-striped table-bordered">}}
56+
| Issue ID | Status |
57+
|----------------|--------|
58+
| 46022 | Won't be resolved |
59+
{{</bootstrap-table>}}
60+
61+
#### Description
62+
63+
Users now see a warning message when they click the **Send Usage To F5** button if no new usage data or report is available. The message reads:
64+
65+
> "Usage data is not available at the moment. Please try submitting usage details again later."
66+
67+
---
68+
69+
70+
## 2.19.1
71+
72+
March 27, 2025
73+
74+
### {{% icon-resolved %}} The certificate stats are not displayed correctly in the Certificates and Keys page as well as the Dashboard page. {#45991}
75+
76+
{{<bootstrap-table "table table-striped table-bordered">}}
77+
| Issue ID | Status |
78+
|----------------|--------|
79+
| 45991 | Fixed in Instance Manager 2.20.0 |
80+
{{</bootstrap-table>}}
81+
82+
#### Description
83+
84+
When the dashboard page and certificates page are loaded, the count displayed for total, valid, expired, expires soon, managed and unmanaged are incorrect.
85+
86+
#### Workaround
87+
88+
The changes required have been made and the UI displays the values correctly now. Pagination also works well along with the certificate stats.
89+
90+
---
91+
92+
1693
## 2.19.0
1794

1895
February 06, 2025
@@ -134,71 +211,19 @@ There is an issue that causes previous error messages to persist in the web inte
134211
---
135212

136213

137-
## 2.17.3
138-
139-
September 13, 2024
140-
141-
### {{% icon-resolved %}} The web interface can't display more than 100 certificates {#45565}
142-
143-
{{<bootstrap-table "table table-striped table-bordered">}}
144-
| Issue ID | Status |
145-
|----------------|--------|
146-
| 45565 | Fixed in Instance Manager 2.19.0 |
147-
{{</bootstrap-table>}}
148-
149-
#### Description
150-
151-
The Certificate Management screen can only show up to 100 certificates.
152-
153-
---
154-
155-
156214
## 2.17.0
157215

158216
July 10, 2024
159217

160-
### {{% icon-resolved %}} Mismatch in date formats in custom date selection on NGINX usage graph {#45512}
161-
162-
{{<bootstrap-table "table table-striped table-bordered">}}
163-
| Issue ID | Status |
164-
|----------------|--------|
165-
| 45512 | Fixed in Instance Manager 2.18.0 |
166-
{{</bootstrap-table>}}
167-
168-
#### Description
169-
170-
The months in the custom date range were not displayed correctly because NGINX Instance Manager assumed the data format was in the US timezone.
171-
172-
---
173-
174-
### {{% icon-resolved %}} NGINX Agent 2.36.0 fails to validate certain NGINX configurations in NGINX Instance Manager 2.17.0 {#45153}
175-
176-
{{<bootstrap-table "table table-striped table-bordered">}}
177-
| Issue ID | Status |
178-
|----------------|--------|
179-
| 45153 | Fixed in nginxagent-2.36.0 |
180-
{{</bootstrap-table>}}
181-
182-
#### Description
183-
184-
In NGINX Instance Manager 2.17.0, an "invalid number of arguments" error appears in the web interface when using specific configuration parameters in NGINX Agent 2.36.0.
185-
186-
#### Workaround
187-
188-
Install NGINX Agent **2.35.1** if you're using NGINX Instance Manager 2.17.0. This version is included with NGINX Instance Manager 2.17.0 by default.
189-
190-
If you're installing NGINX Agent from package files, follow the steps in the [Installing NGINX Agent](https://github.com/nginx/agent?tab=readme-ov-file#installing-nginx-agent-from-package-files) guide.
191-
192-
---
193-
194218
### {{% icon-bug %}} Web Analytics are not enabled after upgrading Instance Manager when keeping existing nms-http.conf {#45131}
195219

196220
{{<bootstrap-table "table table-striped table-bordered">}}
221+
197222
| Issue ID | Status |
198223
|----------------|--------|
199224
| 45131 | Open |
200-
{{</bootstrap-table>}}
201225

226+
{{</bootstrap-table>}}
202227
#### Description
203228

204229
When using NGINX Instance Manager, you configure OIDC by manually editing the /etc/nginx/conf.d/nms-http.conf and /etc/nms/nms.conf files.
@@ -218,11 +243,12 @@ add_header Content-Security-Policy "default-src 'none'; block-all-mixed-content;
218243
### {{% icon-bug %}} Failure to retrieve instance configuration when NAP-enabled instance doesn't register properly {#45113}
219244

220245
{{<bootstrap-table "table table-striped table-bordered">}}
246+
221247
| Issue ID | Status |
222248
|----------------|--------|
223249
| 45113 | Open |
224-
{{</bootstrap-table>}}
225250

251+
{{</bootstrap-table>}}
226252
#### Description
227253

228254
If NGINX Agent is configured to monitor NGINX App Protect before App Protect is installed, NGINX Agent will send an empty App Protect metadata structure to NGINX Instance Manager. This causes Instance Manager to fail to register the NGINX instance properly.
@@ -233,34 +259,6 @@ Edit the "/etc/nginx-agent/nginx-agent.conf" file and configure "precompiled_pub
233259

234260
---
235261

236-
### {{% icon-resolved %}} Failure to notify user when template configuration publish fails {#44975}
237-
238-
{{<bootstrap-table "table table-striped table-bordered">}}
239-
| Issue ID | Status |
240-
|----------------|--------|
241-
| 44975 | Fixed in Instance Manager 2.18.0 |
242-
{{</bootstrap-table>}}
243-
244-
#### Description
245-
246-
When publishing a configuration template fails, the system only displays "Accepted" without providing the final result, such as "Success" or "Failure."
247-
248-
---
249-
250-
### {{% icon-resolved %}} Editing template submissions now allows for using most recent template version {#44971}
251-
252-
{{<bootstrap-table "table table-striped table-bordered">}}
253-
| Issue ID | Status |
254-
|----------------|--------|
255-
| 44971 | Fixed in Instance Manager 2.17.0 |
256-
{{</bootstrap-table>}}
257-
258-
#### Description
259-
260-
When editing a template submission, you can now choose between using a snapshot of the template from when it was first deployed or the latest version of the template. **Important:** Note that if you use the latest version, changes to the templates might make an augment template incompatible with a base template, causing the publication to the data plane to fail.
261-
262-
---
263-
264262

265263
## 2.15.0
266264

0 commit comments

Comments
 (0)