Breadcrumbs

Linux: Upgrading from 23.252 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 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. 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:

      setIfEmpty.png

  • 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