Choose firmware suited to each node's role and purpose, and track download, preparation and deployment progress. The currently running version, target version and health results are each available for review.
Learn about version selectionView compatible releases in Gateway or Connector details and submit a target version for nodes that need an update. The firmware must match the node’s role and purpose; dedicated port forwarding uses its corresponding firmware.
Once the team joins the test channel, the corresponding Beta firmware options become available. Existing nodes are not upgraded automatically as a result; when you need them, select and submit them individually for each node.
The node details show progress through requested, preparing, downloading, preparation complete and deploying stages. After the request is submitted or the download finishes, you must still wait for the node to deploy the target release.
Only after the node reports a matching running version and release information and passes the relevant health checks is the corresponding completion result shown. If an upgrade fails, review the specific reason, and if you need to try again, explicitly initiate a retry.
Firmware upgrades and dedicated-purpose switching may interrupt associated connections, so schedule maintenance according to your business needs. Restoring service with the current firmware is a separate maintenance operation.
Learn about node service restoration →Version locking is managed by platform administrators, and the customer console displays the lock status. Locked nodes keep the current version, and upgrades, service restoration and purpose switching are blocked.
To adjust the lock, contact support; when updating, choose a release version that is available and compatible with this node.
No. Joining only opens up the corresponding test firmware options; existing nodes, Relays and running versions are retained. If you need a test release, select the target version on the node page and submit the upgrade.
Not yet. Downloading and preparation are intermediate stages; the node also needs to apply the update, report a matching running version and release information, and pass the relevant health checks. Determine the result from the current version, target version and application status.
Version locking is managed by platform administrators, and the customer page displays the status. During locking, upgrades, restoration and purpose switching are restricted; contact support to make adjustments.
