Skip to content
X-Edge AI

Frontend / backend version mismatch

Symptom

Section titled “Symptom”

In Settings → About, the Backend Version row is shown in amber, with a hint that the frontend and backend versions differ.

What the rows mean

Section titled “What the rows mean”

The About panel shows three versions:

  • Release — the release the box installed, written by the installer from the bundle. This is the answer to “what version is this box”.
  • Frontend Version — the version compiled into the frontend bundle you are viewing.
  • Backend Version — the version compiled into the backend image.

A release reuses the previous image for a service that did not change. The frontend and backend build versions can therefore differ on a correctly updated box. The amber highlight compares only those two build versions, so on its own it does not mean anything is wrong.

Confirm

Section titled “Confirm”

Ask the box which release it runs and which backend build it carries:

Terminal window
curl -s http://localhost:5000/api/system/health | jq '{releaseVersion, version, commit}'
  • releaseVersion matches the bundle you installed → the update is complete. The amber row only reflects a service that was carried over unchanged.
  • releaseVersion is older than the bundle you installed, or is null → the update did not finish, or the box was installed by a release older than release reporting.

Fix

Section titled “Fix”

  1. Rule out a stale browser tab. The frontend version is fixed when the page loads. Hard-refresh the browser (reload ignoring the cache) and check Settings → About again.

  2. If the Release row is not the release you installed, run the update again from that release’s bundle directory:

    Terminal window
    sudo ./update.sh

    The update brings frontend, backend and inference up together from the bundle’s images.

  3. Verify. Reload Settings → About. The Release row should show the release you installed.

Prevent

Section titled “Prevent”
  • Update from the release bundle, not container by container. update.sh keeps the three services in step with the release.
  • Read the Release row after every update. It is the post-update check; the build-version rows are for support.
Section titled “Related”