From e58705a12dd9c34162b61c3214ae7692fcba5baf Mon Sep 17 00:00:00 2001 From: fiorucci Date: Tue, 29 Apr 2025 21:18:02 +0100 Subject: [PATCH] Fixed broken anchor --- content/nim/nginx-app-protect/setup-waf-config-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nim/nginx-app-protect/setup-waf-config-management.md b/content/nim/nginx-app-protect/setup-waf-config-management.md index ddc59f165..3fab29ebe 100644 --- a/content/nim/nginx-app-protect/setup-waf-config-management.md +++ b/content/nim/nginx-app-protect/setup-waf-config-management.md @@ -244,7 +244,7 @@ This typically happens when: - A managed instance is upgraded to a new NGINX App Protect WAF version. - You add a new instance running a different version of NGINX App Protect WAF. -To enable this automatic download feature, you need to [upload your NGINX App Protect WAF certificate and key](#upload-nginx-app-protect-waf-certificate-and-key) to NGINX Instance Manager. This step allows Instance Manager to securely connect to the NGINX package repository and retrieve the necessary files. You only need to upload the certificate and key once. +To enable this automatic download feature, you need to [upload your NGINX App Protect WAF certificate and key](#upload-the-nginx-app-protect-waf-certificate-and-key) to NGINX Instance Manager. This step allows Instance Manager to securely connect to the NGINX package repository and retrieve the necessary files. You only need to upload the certificate and key once. If the certificate is missing or invalid, or if NGINX Instance Manager can’t connect to the repository, you’ll see an error like: