Install server updates

The Updates tab, under More on the server's page, lists the plugins, mods, datapacks and Bedrock packs on your server that have a newer build. It covers what you installed from the marketplace, since we know where each of those came from. Files you uploaded yourself are not checked.

• The server software and a modpack are not listed here. Move those to a new version under Server software on the Software tab, as Change the server software describes. A Bedrock Dedicated Server shows Update available on its Current software card instead (Run a Bedrock Dedicated Server).
• On a server someone shared with you, installing an update needs the Install software permission.

1. In the dashboard, go to App Deployment and open the server, then the Updates tab.
2. Read the list. Each row shows the Package, the Current build on the server, the build that is Available and the Source it comes from.
3. To check again, select the refresh button next to the title.

We only offer a build that fits the server's software and game version. We prefer release builds over beta and alpha builds, and offer a build only when it is newer than the one installed.

1. On the Updates tab, find the row of the addon you want to update.
2. Select Install on its row. To update everything in the list, select Install all at the top right.
3. Wait for the message Update to <name> <version> queued. (or All updates queued.). The install runs as a job, which the Software tab follows.

Install all queues the updates one after another. A server accepts 8 install requests every 10 minutes, so with more than 8 updates the tab queues the first 8 and then shows Queued 8 of 12 updates, then could not queue the next one: Too many requests for this action. Try again later. Wait 10 minutes and select Install all again for the rest.

We remove the old file and install the new build as one job, so the plugin is never loaded twice. The new build loads the next time the server starts.

You can also update an addon from the Software tab: open Installed addons, find the addon (a row with an update shows a badge such as Update to 2.11.0) and select Update. Manage installed addons has the details.

When every tracked addon is on its newest compatible build, the tab shows Everything is up to date.

Could not queue the update

We did not queue the install. The message names the reason, for example that you do not have the Install software permission on a shared server, or that the server reached its limit of 8 install requests in 10 minutes. Fix that, or wait 10 minutes, and select Install again.

Could not check for updates

We could not reach a source to compare builds. Select Try again, or check again later.

An addon you installed is missing from the list

The list shows only addons with a newer build that fits your server. A file you uploaded yourself, or copied in with an import, is never checked.

• Manage installed addons
• Install plugins, mods and modpacks
• Change the server software

GET /api/v1/client/servers/{uuid}/updates returns {"updates": […]} with one entry per addon that has a newer build:

{
  "updates": [
    {
      "record_uuid": "3f2c8a61-0d4e-4b7a-9e15-6a2b7c9d0e41",
      "display_name": "LuckPerms",
      "kind": "plugin",
      "source_name": "Modrinth",
      "install_path": "/plugins/LuckPerms-Bukkit-5.4.141.jar",
      "current_version": "vKq6e7Sf",
      "current_version_name": "5.4.141",
      "latest_version": "Rk3eYx1m",
      "latest": {"version_id": "Rk3eYx1m", "name": "5.4.145", "release_date": "2026-09-12T08:30:00Z", "version_type": "release"},
      "update_available": true,
      "checked_at": "2026-09-25T14:30:00+00:00"
    }
  ]
}

current_version and latest_version are the source's own build ids, and current_version_name and latest.name are the version names people read. kind is one of plugin, mod, datapack, bedrock_addon or bedrock_resource_pack. We leave out an addon whose kind we cannot tell. To install an update, send POST /api/v1/client/servers/{uuid}/software/install with the entry's source_uuid, identifier and kind, its latest_version as version, and "mode": "update" so the old file is removed. You can also send POST /api/v1/client/servers/{uuid}/software/{record_uuid}/update with the entry's record_uuid, as Manage installed addons shows. GET /api/v1/client/servers/{uuid}/software/updates gives the same check with more options.

Any user on the server can read the list.