Skip to main content
Version: v1.1

Manual update of invalid Unit certificates

Update with aos-prov CLI tool (for AosVM only)​

  1. Install aos-prov CLI tool version 5.4.2 or higher.

    Checking the tool version

    To check the tool is the latest version run command:

    ~/.aos/venv/Scripts/python -m aos_prov check-version

    Empty output means the tool is up to date.

    You can update to the latest version with command:

    ~/.aos/venv/Scripts/python -m pip install --upgrade aos-keys aos-signer aos-prov

  2. Find the group name of your Unit: Open VirtualBox and find the name of your group like on screenshot: screenshot

  3. Start command prompt and run command:

    ~/.aos/venv/Scripts/python -m aos_prov fix-unit --name {GROUP_NAME}

    # Example from the screenshot:
    ~/.aos/venv/Scripts/python -m aos_prov fix-unit --name devStable

  4. Wait till script finishes.

Update with manual procedure (generic)​

  1. Start each node of the Unit.

  2. Find SSH ports for each node: refer to docs

  3. Execute command for each node, replacing port from previous step.

    ssh root@localhost -p {PORT} "systemctl stop systemd-timesyncd && date -s '2026-06-27' && systemctl restart aos.target"

  4. Login to https://oem.aoscloud.io/oem/units portal and Open your unit details page.

  5. Wait till Unit went online (see screenshot below)

  6. Click Renew unit Certificates on Certificates tab.

  7. Wait till all certificates receive status renew_done

  8. Reboot each node or execute command for each node, replacing port from step 2.

    ssh root@localhost -p {PORT} "reboot now"

screenshot