Linux: Upgrading from 23.261 to the Latest Version

The current version of FileCloud runs FIPS mode using FIPS 140-3, which does not support encrypted managed storage on RHEL9. If you are planning to use FileCloud on RHEL9 in FIPS mode, please Contact FileCloud Support .

If you are running FileCloud in a high availability environment, to upgrade to the latest version, please Contact FileCloud Support.

FileCloud Support can help you upgrade or can provide a PDF with instructions if you would like to perform the upgrade without assistance.

Pre-upgrade

As always, make a full backup of your existing installation before upgrading.
Backup on Linux
If you are running in a high-availability environment with separate MongoDB servers, upgrade to MongoDB version 8 if you have not upgraded already. Please Contact FileCloud Support if you need more information.
If you initially installed FileCloud before version 23.242
AND
You have not upgraded to FileCloud version 23.261.1 or 23.261.2
You must change your MongoDB Feature Compatibility Version from 6.0 to 7.0 by running the applicable command below, or MongoDB will not start.

If MongoDB authentication is not enabled:
```
mongosh --eval 'db.adminCommand({setFeatureCompatibilityVersion: "7.0"})'
```
If MongoDB authentication is enabled:
(Replace PASSWORD with your MongoDB admin password)
```
mongosh -u admin -p 'PASSWORD' --authenticationDatabase admin \
  --eval 'db.adminCommand({setFeatureCompatibilityVersion: "7.0"})'
```
After you run one of the above commands, verify that the current Feature Compatibility Version is 7.0 by running the following command and checking the value it returns:
```
mongosh --quiet --eval 'db.adminCommand({getParameter:1,featureCompatibilityVersion:1})'
```
If you are using native LDAP for authentication and using non-TLS connections set the LDAP Host value to ldap://hostname. Older FileCloud versions supported host value without the protocol definition ldap://
If your system uses ServerLink, follow these steps:
1. Before upgrade, ensure all ServerLink nodes are fully synced and are at the same state.
2. Make backups of all nodes as needed.
3. Stop the FileCloud ServerLink client service in secondary nodes.
4. Upgrade the primary node first.
5. Upgrade each secondary node after upgrading the primary node.
6. Start the FileCloud ServerLink client service in secondary nodes. (In HA setups, client service must run only in one of the servers from each secondary node.)

Note: All connected ServerLink nodes, both primary and secondary, must be upgraded to the same ServerLink version before enabling access to the site again.

Upgrade instructions

Upgrade using the steps at Upgrade FileCloud on Linux .

Post-upgrade

Add ../scratch/tmp folder

warning The folder ../scratch/tmp is not recreated in FileCloud, causing the system to fail to save necessary short-term data. After FileCloud is upgraded, add the folder /var/www/html/scratch/tmp to avoid any issues.

FileCloud iOS mobile users

Beginning with FileCloud Server version 23.261, iOS users must be on iOS 16+ and app version 23.261+.