diff --git a/site/content/how-to/monitoring/troubleshooting.md b/site/content/how-to/monitoring/troubleshooting.md index 20b96d9c8d..5c8cc89e4c 100644 --- a/site/content/how-to/monitoring/troubleshooting.md +++ b/site/content/how-to/monitoring/troubleshooting.md @@ -367,7 +367,7 @@ To **resolve** this issue you will need to set `allowPrivilegeEscalation` to `tr ##### NGINX Plus failure to start or traffic interruptions -Beginning with NGINX Gateway Fabric 1.5.1, NGINX Plus requires a valid JSON Web Token (JWT) to run. If this is not set up properly, or your JWT token has expired, you may see errors in the NGINX logs that look like the following: +Beginning with NGINX Gateway Fabric 1.5.0, NGINX Plus requires a valid JSON Web Token (JWT) to run. If this is not set up properly, or your JWT token has expired, you may see errors in the NGINX logs that look like the following: ```text nginx: [error] invalid license token diff --git a/site/content/installation/nginx-plus-jwt.md b/site/content/installation/nginx-plus-jwt.md index a2f79792a1..9dd39f4e9e 100644 --- a/site/content/installation/nginx-plus-jwt.md +++ b/site/content/installation/nginx-plus-jwt.md @@ -230,7 +230,7 @@ Replace the contents of `` with the contents of the JWT token itself. You can then pull the image: ```shell -docker pull private-registry.nginx.com/nginx-gateway-fabric/nginx-plus:1.4.0 +docker pull private-registry.nginx.com/nginx-gateway-fabric/nginx-plus:1.5.1 ``` Once you have successfully pulled the image, you can tag it as needed, then push it to a different container registry.