Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update version in docker pull #2919

Merged
merged 2 commits into from
Dec 16, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion site/content/how-to/monitoring/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -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:
sjberman marked this conversation as resolved.
Show resolved Hide resolved
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
Expand Down
2 changes: 1 addition & 1 deletion site/content/installation/nginx-plus-jwt.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,7 +230,7 @@ Replace the contents of `<JWT Token>` 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.
Expand Down
Loading