Upgrading FineOps over the Internet- FineOps Help Document

Last update: 2026-11-04

Overview

Version

FineOps Version	Functional Change
V2.0.0	Optimized the interaction by adjusting the function entry location.
V2.20.0	Supported automatic upgrades of FineOps in an Internet-connected environment.
V2.21.0	Arranged functions in separate rows.

Function Description

This document provides a solution to upgrade FineOps and its dependent O&M components by downloading images online. This method applies to environments where the image repository can connect to the FanRuan cloud repository.

Note:

1. If the image repository cannot access the FanRuan cloud repository, see Upgrading FineOps on the Internal Network.

2. This document does not apply to application version upgrades for FineReport or FineBI projects. For details, see Upgrading O&M Projects over the Internet.

3. Before upgrading FineOps, you can check recent functional changes. For details, see Update History.

Upgrade Method Selection

Comparison Item	Manual Upgrade	Automatic Upgrade
Application scenario	Upgrade FineOps immediately.	Upgrade FineOps during a fixed maintenance window.
Trigger method	Click Upgrade Now.	The upgrade is triggered at the specified time when a new version is available.
Follow-up operation	Restart FineOps and then upgrade the O&M components after the upgrade is complete.	Check the results of the FineOps restart and component upgrades after the automatic upgrade. Do not treat scheduled task triggering as upgrade completion.

Checking Upgrade Prerequisites

Check Item	Description
Image repository connectivity	The server where the image repository is located must be able to pull images from the FanRuan cloud repository. Otherwise, the online upgrade method in this document cannot be used. For details, see Ensuring Access to FanRuan Cloud Repository.
New version availability	Choose Platform Management > Update & Upgrade and check whether a new version is available. If the current version is already the latest, no upgrade is required.
Docker engine	From V1.9.0, the Docker engine version is automatically checked before upgrade. If the prompt "The version of the docker engine at the xx node is too low, and an online upgrade to a higher version is not supported currently. Use the tool to upgrade it offline." appears, do not continue the online upgrade. Use FineKey for offline upgrade instead. For details, see Upgrade FineOps on the Internal Network.
Maintenance time	FineOps cannot be accessed during a restart, and you need to log in again after the restart. Perform the upgrade during a time window when platform access can be interrupted.
Parallel tasks	Automatic upgrade may conflict with project backup, upgrade, deployment, scaling, or uninstallation. Avoid these operations when setting the upgrade time.

Manual Upgrade

Checking New Version Availability

1. Log in to FineOps as the admin and choose Platform Management > Update & Upgrade.

If automatic upgrade is disabled and a new version is available, you can also click View Upgrade in the New Version Available pop-up window to go to the upgrade entry.

2. Check the current version, new version, and release notes.

Prompt	Description
New Version Available	A new version of FineOps is available. You can click this button to view the upgrade log.
Already Latest Version	No upgrade is required.
Upgrade Unavailable Due to Network Issues	Online upgrade cannot be used. First, check repository connectivity according to the "Checking Upgrade Prerequisites" section. For a pure internal-network environment, use offline upgrade.

Upgrading and Restarting FineOps

Note:

FineOps cannot be accessed before the restart succeeds. Confirm that platform access can be interrupted before the restart.

1. Click New Version Available and click Upgrade Now.

The Upgrade Now button is grayed out during the upgrade, and the button text changes to Upgrading.

2. After the successful upgrade, the prompt "Upgraded successfully." is displayed, the button becomes clickable again, and the button text changes to Restart Now.

3. Click Restart Now. If you choose to restart FineOps later, complete the restart during an allowed interruption window.

Upgrading O&M Components

After FineOps is upgraded and restarted, you must upgrade the O&M components required by this version. The overall upgrade is complete only after these components are upgraded.

1. Log in to FineOps as the admin.

2. If the prompt "The FineOps upgrade is at the final step, and this page will be automatically refreshed after the upgrade is completed. Do not close FineOps during the upgrade!" appears, wait until the automatic upgrade is complete and do not close FineOps during the upgrade.

3. If no automatic upgrade prompt appears, or if the prompt "Some components failed to be upgraded. Upgrade these components manually in O&M Component." appears, click Go to O&M Component, or choose Platform Management > O&M Component.

4. Click One-Click Upgrade to trigger the remaining component upgrades again.

Checking Whether the Upgrade is Successful

1. Log in to FineOps as the admin.

2. Choose Platform Management > Update & Upgrade to view the version. Already Latest Version means that FineOps has been successfully upgraded.

Automatic Upgrade

From FineOps V2.20.0, automatic upgrades are supported.

Note:

You are advised to enable Automatic Upgrade so that the latest O&M updates can be applied to your applications in time.

Setting Upgrade Time

1. Choose Platform Management > Update & Upgrade.

2. Enable Automatic Upgrade and set the upgrade time to a time window when platform access can be interrupted and no project maintenance task is running.

3. Click OK.

Setting Item	Description
Automatic Upgrade	It is enabled by default.
Upgrade Time	It defaults to Every Week Saturday 01:00:00. The time can be adjusted.

Following Up on Automatic Upgrade Results

When a new version is available, FineOps performs the upgrade at the specified time.

If the New Version Available dialog appears when you log in, you can also click Adjust Upgrade Time to change the upgrade time.

Upgrading O&M Components

After FineOps is upgraded and restarted, you must upgrade the O&M components required by this version. The overall upgrade is complete only after these components are upgraded.

1. Log in to FineOps as the admin.

4. Click One-Click Upgrade to trigger the remaining component upgrades again.

Checking Whether the Upgrade is Successful

1. Log in to FineOps as the admin.

2. Choose Platform Management > Update & Upgrade to view the version. Already Latest Version means that FineOps has been successfully upgraded.

Upgrade Failure Troubleshooting

Whether the upgrade is performed manually or automatically, if the overall FineOps upgrade or the upgrade of some components fails, a dialog box appears after you log in to FineOps as an admin, as shown in the following figure:

Overall FineOps upgrade failure: The upgrade failed. The retry will be performed in the next upgrade cycle. You can also contact technical support for help.
O&M component upgrade failure: Some components failed to be upgraded. Upgrade these components manually in O&M Component.

Click View Details to be redirected to the Update & Upgrade tab page under Platform Management > O&M Component, where you can view the upgrade details.

The upgrade records show the versions before and after the upgrade, the image download duration, the upgrade duration, the upgrade result, and the failure cause.

The following table lists possible failure causes and their solutions.

Failure Cause	Analysis & Solution
Automatic Upgrade conflicts with operations on the project.	The automatic upgrade will fail if it runs simultaneously with operations on the project, such as backup, upgrade, deployment, scaling, and uninstallation, and the platform will retry the upgrade. If all five retries fail, the current upgrade is considered failed and will be retried in the next cycle. For example, if an admin is scaling the project during the scheduled upgrade time on Saturday and all five retries fail, the upgrade is retried on the next Saturday.
Some O&M components failed to be upgraded.	After FineOps is upgraded, the latest O&M component images required by the new version are automatically obtained. The overall FineOps upgrade is considered successful only after all O&M components are upgraded. If the message "Some components failed to be upgraded. Upgrade these components manually in O&M Component." appears, choose Go to O&M Component > One-Click Upgrade to manually upgrade the remaining components.

Failure Cause

Analysis & Solution

Automatic Upgrade conflicts with operations on the project.

The automatic upgrade will fail if it runs simultaneously with operations on the project, such as backup, upgrade, deployment, scaling, and uninstallation, and the platform will retry the upgrade. If all five retries fail, the current upgrade is considered failed and will be retried in the next cycle.

For example, if an admin is scaling the project during the scheduled upgrade time on Saturday and all five retries fail, the upgrade is retried on the next Saturday.

Some O&M components failed to be upgraded.

After FineOps is upgraded, the latest O&M component images required by the new version are automatically obtained. The overall FineOps upgrade is considered successful only after all O&M components are upgraded.

If the message "Some components failed to be upgraded. Upgrade these components manually in O&M Component." appears, choose Go to O&M Component > One-Click Upgrade to manually upgrade the remaining components.