# Firmware Update

The **CloudBox** is designed to keep its system software up to date automatically. When connected to the internet, the CloudBox checks for available firmware updates. These updates are essential for ensuring optimal performance, security, and access to new features. However, updates are only applied when the user manually selects the option to reboot and install the new firmware. This article will guide you through the firmware update process and what to expect during the update.

**IMPORTANT**: The update **requires a stable internet connection** (4G connectivity is not supported for firmware updates) and the system in **sync with the current date time**. Make sure the CloudBox is connected via **Ethernet** or a reliable **WiFi** network and has the **NTP sync enabled**.

<figure><img src="/files/EhecmUNu9KOD0lO9t5sM" alt=""><figcaption></figcaption></figure>

## Firmware Update Notification

When the CloudBox detects a new firmware version, the update will be shown in the **Status Interface** under the **Updates** section.&#x20;

<figure><img src="/files/nKd2J0pkAz1zJVsFMdrx" alt=""><figcaption></figcaption></figure>

The following information is displayed:

* **New backend version**: The version number of the backend software that is available for update.
* **New front version**: The version number of the frontend software available for update.

The user is notified of the availability of the update but must initiate the update process manually by selecting the **Reboot and Install** option.

## How to Install a Firmware Update

1. **Check for Update Availability**:
   * Go to the **Status Interface** on the CloudBox web dashboard.
   * If a new firmware version is available, it will be displayed in the **System Update Available** section at the bottom of the interface.
2. **Select "Reboot and Install"**:

   * To proceed with the update, toggle the **Reboot and Install** option.
   * The CloudBox will reboot to start the installation of the new firmware. Ensure the device is connected to a stable internet connection during this process.

   **IMPORTANT**: The update **requires a stable internet connection** (4G connectivity is not supported for firmware updates) and the system in **sync with the current date time**. Make sure the CloudBox is connected via **Ethernet** or a reliable **WiFi** network and has the **NTP sync enabled**.
3. **Monitor the Installation Progress**:
   * During the installation, the system will reboot.
   * After rebooting, you can reconnect to the CloudBox by navigating to `http://cloudbox.local:3000` or using the **Ethernet IP address**, for example: `http://192.168.1.10:3000`. The CloudBox interface will display the progress of the update.
4. **Post-Installation**:
   * Once the update is complete, the CloudBox will automatically restart.
   * The system will return to normal operation, and the new firmware versions will be active.

## Automatic Rollback Protection

The CloudBox provides **rollback protection** during the update process. When a new firmware version is installed, the previous version is **backed up and stored** in case of an issue with the new firmware. This allows the user to roll back to the previous version if necessary, ensuring that the device remains operational even in the rare case of a failed update.

## LED Signal During Update

During the firmware update, the **Start LED** will blink **every 3000 ms** to indicate that the system is updating. The CloudBox will not be operational for timing sessions during the update. Once the update is completed and the system reboots, the LED will return to its normal state depending on the system status (solid red for standby or blue during a session).

## Considerations for a Successful Update

* **Stable Internet Connection**: Ensure that the CloudBox has a stable internet connection throughout the update process. **4G connectivity and Wifi are not supported** for firmware updates, so make sure the device is connected via Ethernet to a reliable network.
* **NTP service enabled**: Ensure that the system date and time are current, otherwise the firmware download will fail.
* **Accessing the CloudBox After Reboot**: Once the update process starts and the system reboots, reconnect to the CloudBox via `cloudbox.local` or its fixed IP address.
* **Backup of the Previous Firmware Version**: The CloudBox automatically backs up the current firmware before installing a new one. This ensures that if anything goes wrong during the update, the system can revert to the previous working version.
* **No Timing Sessions During Update**: The CloudBox will not be able to start or stop timing sessions during the update process. Make sure no critical timing tasks are running before initiating the update.

## Summary

The **CloudBox firmware update process** is designed to be simple and secure. When a new update is detected, the user can choose when to install it by selecting the **Reboot and Install** option. The system will then reboot and install the new firmware while backing up the previous version to safeguard against any issues. During the update, the **Start LED** will blink to show that the system is updating, and users can follow the installation progress by reconnecting to the CloudBox web interface. Always ensure the CloudBox has a stable internet connection during the update process for a smooth and successful installation.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.runonrufus.com/rufus-cloudbox/advanced-operations/firmware-update.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
