Linux: Upgrading from 23.251 to the Latest Version

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

1. As always, make a full backup of your existing installation before upgrading.
   Backup on Linux

2. 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.

3. 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})'
   

4. 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://

5. Beginning in FileCloud 23.253, by default, a more granular dynamic content security policy replaces the existing content security policy in the .htaccess file. If you are upgrading, to make this change effective, you must make a small change to the Content-Security-Policy header in the .htaccess file:

   • Open the .htaccess file.

     in Windows:
     C:\xampp\htdocs\.htaccess

     in Linux:
     /var/www/html/.htaccess

   • Find the line that begins:
     Header set Content-Security-Policy:

   • Change set to setifempty:
     Header setifempty Content-Security-Policy:

     

6. If you have added custom rules to the .htaccess file, they will be overridden by the dynamic CSP feature. To solve this:
   Either:
   Disable the dynamic CSP feature with the setting TONIDOCLOUD_DYNAMIC_CSP_ENABLED. See Dynamic CSP in FileCloud.

   Or:
   Add the custom rules to the setting TONIDOCLOUD_DYNAMIC_CSP_EXTEND.

   To add the custom rules:

   1. On the FileCloud Server, open the cloudconfig file:

      In Windows:
      C:\xampp\htdocs\config\cloudconfig.php

      In Linux:

      /var/www/html/config/cloudconfig.php

   2. Add the setting in the format:

      define("TONIDOCLOUD_DYNAMIC_CSP_EXTEND",directive:source,source;[directive:source,source;]);
      

      
      

      for example:

      define("TONIDOCLOUD_DYNAMIC_CSP_EXTEND", "script-src:amazon.com;worker-src:amazon.com,google.com;");
      

       

7. Beginning with version 23.252, a new group, Externals, automatically includes all External users, and the Everyone group does not include External users. External users who were include in the Everyone group in earlier versions of FileCloud are no longer included in it.
   
   The Externals group functions to prevent External users from having the same share, folder, and policy access as users in the Everyone group. 
   
   Previously created DLP rules that denied access to the Everyone group will now deny access to both the Everyone and Externals groups. Previously created DLP rules that allowed access to the Everyone group will continue to allow access to the Everyone group and not to the Externals group.
   
   If your use cases require that external users have the same access to files and folders as other users, you can give the Externals group the same permissions as the Everyone group by running the tool assignexternalsgroup.php.  See Assign the Externals Group the Same File Access as the Everyone Group for help.

8. 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

• To upgrade FileCloud from 23.251 to the latest version in Linux see Upgrade FileCloud on Linux. (You cannot upgrade using the Admin Portal.)

Post-upgrade

Add ..\scratch\tmp folder

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+.