Breadcrumbs

Linux: Upgrading from 23.242 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 FileCloud in a high availability or multi-server environment, verify that the MongoDB feature compatibility version is set to version 6. If not, set MongoDB feature compatibility to version 6 by following the instructions at https://www.mongodb.com/docs/manual/reference/command/setFeatureCompatibilityVersion/ or contacting FileCloud support.

  • 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://

  • Beginning in FileCloud 23.253, by default, a more granular dynamic content security policy replaces the existing content security policy in the .htaccess file. 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:

      setIfEmpty.png
  • 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.

  • Prior to version 23.241, FileCloud always used the AD attribute mail to authenticate AD users, even if the AD mail attribute field in FileCloud specified a different attribute.

    This has been fixed.
    However, if you used an AD attribute other than the mail prior to the current version, AD users imported into FileCloud prior to the current version will now receive an error when they try to log in to FileCloud (unless the non-mail attribute always has the same value as the mail attribute). If you have users who may have trouble logging in for this reason, prior to updating, change the AD mail attribute field back to mail.

  • 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.242 to the latest version in Linux see Upgrade FileCloud on Linux . (You cannot upgrade using the Admin Portal.)

Post upgrade

For systems running in a high availability or multi-server environment

Upgrade instructions for the FileCloud 23.242 Outlook Add-in 

If you plan to use the updated FileCloud Outlook Add-in, if you have previously modified the default values for Access-Control-Allow-origin or Access-Control-Allow-Credentials, they may not be set to the values required to run the FileCloud Outlook Add-in. After updating the Outlook Add-in, open .htaccess and make sure these settings have the values indicated below.

To check/replace the htaccess settings:

  1. Open the .htacess file:
    Linux: /var/www/html/.htaccess

  2. If the following commands are missing or are present, but set to different values, set them as follows:

    Header always set Access-Control-Allow-Origin ffol.filecloud.com 
    Header set Access-Control-Allow-Credentials true