Requirements

Beginning with FileCloud 23.1, FileCloud no longer supports Ubuntu 18.04/20.04, CentOS 7/RHEL 7 and RHEL 8. In addition, FileCloud no longer supports Debian. If you are using any of those OS versions, please migrate to Ubuntu 22.04 LTS or RHEL 9.
Beginning with FileCloud 23.1, Linux installation and upgrades moved to a new repository system.
The OS’s we currently support are:
Ubuntu 22.04 LTS
RHEL 9.x
Since support for OpenSSL 1.1.1 ends on September 11, 2023, FileCloud 23.1 uses OpenSSL 3.0. which is not available for previous Linux versions, and therefore FileCloud requires installation or update on the Linux versions listed above.

MongoDB 6 requires use of the AVX instruction set, which is available on select Intel and AMD processors.
If your CPU doesn't have the AVX instruction set, MongoDB 6 will not run.

To check whether your CPU has the instruction set, run:

#lscpu | grep -i avx"

The ability to support FIPS licenses is available in FileCloud Server version 18.2 and later.

To prepare your environment for FileCloud, make sure that you have the required components.

Supported operating systems, installed software, and supported browsers

FileCloud Server now supports FIPS licenses in version 18.2 and later.

Enterprises who are subject to the FIPS regulations must install and run a FIPS-enabled operating system. For example, CentOS in FIPS mode.

When using a FIPS-enabled license, FileCloud Admins will see in the Admin Portal:

Running in FIPS mode is prominently displayed
SSO features are hidden
Storage encryption option is always shown

FileCloud - supported operating systems

To run FileCloud, use one of the following supported operating systems:

Windows Server 2016, Windows Server 2019, Windows Server 2022
Ubuntu 22.04
RHEL 9.0 onwards

For additional options to install on AWS/Azure, see the Installation page.

Additionally, FileCloud can be run inside a Virtual Machine that can be hosted in almost any operating system including macOS.

Client and mobile apps - supported operating systems

Client App	Minimum Supported Version	Latest Supported version
FileCloud Desktop (Beta)	Monterey 12.6.3	Sonoma 14.0
FileCloud Sync	Windows 10 Monterey 12.7	Windows 11 Sonoma 14.0
FileCloud Drive	Windows 10 Monterey 12.7	Windows 11 Sonoma 14.0
FileCloud Outlook Add-in	Office 2018	Office 365 / Office 2021
FileCloud for Office	Office 2019	Office 365 / Office 2021
FileCloud ServerSync	Windows 10	Windows 11
FileCloud Gmail Chrome Extension	Chrome 88	Chrome 117
Save to FileCloud Chrome Extension	Chrome 88	Chrome 118
FileCloud Secure Viewer	Windows 10	Windows 11
FileCloud Desktop Edit	Windows 10 Monterey 12.7	Sonoma 14.0 Windows 11
FileCloud for iPhone	iOS 14	iOS 17
FileCloud for iPad	iOS 14	iOS 17
FileCloud for Android	Android 6	Android 13
Microsoft Edge Web Client	Microsoft Edge v76	Microsoft Edge v117
Google Chrome Web Client	Google Chrome 55.0	Google Chrome 118.0
Mozilla FireFox Web Client	Mozilla Firefox 52	Mozilla Firefox 118
Safari Web Client	Safari 11	Safari 17

Supported Browsers

Microsoft Edge 15 and above
Google Chrome 55.0 and above
Mozilla Firefox 52 and above
Safari 11 and above

Required hardware

Small Installations (~ 100 users)

Intel(R) Xeon(R) CPU E5-2630L v2 or equivalent Quad Core CPUs (2 GHz or higher) (Higher the better depending on additional configuration such as indexers, SOLr, Preview services etc)
Windows: 16 GB of RAM (higher is better) Linux: 16 GB (higher is better)
Storage can be from Physical Disk, SAN, NAS etc
Free disk space as needed

Larger Installations

To support FileCloud, you might need to setup more powerful configurations to include the following:

Use redundant object storage systems like open stack or Amazon S3
Use an HA configuration with a database cluster when running a system with many users

Necessary network configurations

If you are using a load balancer, the HTTP response timeout must be set to 5 minutes or more.

Ports

The following are the ports necessary for the operation for FileCloud.

Port No	Purpose	Internal/External	Remarks
80	HTTP Traffic	External	Port used for http traffic from all clients such as browser, FileCloud sync, FileCloud drive etc., This port should be opened to WAN if clients needs to access FileCloud over internet. For Production, Plain HTTP is NOT RECOMMENDED. ONLY SSL should be used.
443	HTTPS Traffic	External	Port used for https traffic from all clients such as browser, FileCloud sync, FileCloud drive etc., This port should be opened to WAN if clients needs to access FileCloud over internet.
389	LDAP	Internal	Optional port needed if FileCloud users needs to be authenticated against Active Directory or LDAP server This port need not be opened to WAN, as only FileCloud server will be using it within LAN.
636	LDAP SSL	Internal	Optional port needed if FileCloud users needs to be authenticated against a secure Active Directory or LDAP server This port need not be opened to WAN, as only FileCloud server will be using it within LAN.

If MongoDB is set to run on a different computer from the Webserver , then Port 27017 on the computer running MongoDB must be accessible from the Webserver computer in order for it to connect.,

Configuration

Component	Configuration
IP Address	You need a public IP for the server running FileCloud. Typically, this means you need a static IP for the server as dynamic IPs provided by most ISPs keep changing.
Network Connection	You need a good quality network connection to the FileCloud Server. Minimum should be 512 Kbps upload and download for good experience. The faster the connection the better the experience.
Domain Name	You will typically need a top level domain name. For example: cloud.mycompany.com or mycompanycloud.com. You can purchase a domain name from any domain registrar and then point the DNS for that domain name to the public IP of the server that is running FileCloud.
SSL Certificate	You will also need a valid SSL certificate for your domain name to setup and use https with your filecloud server for best security.