Integrations

Integration settings are at Admin → Integrations.

GitHub personal access token

Nexus uses the GitHub API to install and update extensions and themes. Without a token, the GitHub API allows only 60 unauthenticated requests per hour per IP address. With a token, that limit rises to 5,000 per hour.

Why this matters: Every extension install, update check, and theme install makes one or more GitHub API requests. A forum with several extensions checking for updates, combined with server restarts that reload the tarball cache, can exhaust the unauthenticated limit quickly. When the limit is hit, extension and theme operations fail with a download_failed status until the limit resets.

Configuring a token is strongly recommended for any production install.

Creating a token

Go to github.com/settings/tokens
Click Generate new token → Generate new token (classic)
Give it a descriptive name — e.g. Nexus forum
Set an expiration — or choose No expiration for a set-and-forget setup
Under Select scopes, check public_repo — this is the only permission required. It grants read access to public repository data including releases.
Click Generate token and copy it immediately — GitHub only shows it once

Adding the token to Nexus

In Admin → Integrations, paste the token into the Personal access token field and click Save. The token is stored securely and never exposed to the frontend.

The token takes effect immediately — the next extension or theme operation will use it.

Keeping the token current

GitHub tokens with expiry dates stop working when they expire, causing all extension and theme operations to fail with download_failed. Set a calendar reminder before your token’s expiry date to rotate it.

If you use a token with no expiration, consider rotating it periodically as a security best practice.

OAuth providers

OAuth sign-in configuration (GitHub and Google) is also under Admin → Integrations. See the dedicated setup guides: