For a straightforward Ubuntu 24.04 deployment, use ONLYOFFICE’s official Workspace Community installer with Docker and omit the Mail component unless you have a domain and plan to run email. Before you begin, check the server resources and free ports: ONLYOFFICE lists at least 8 GB RAM, 40 GB free disk space, and a 4-core CPU as minimums for this resource-intensive setup.
ONLYOFFICE Workspace combines document editing with collaboration tools. The Community edition is the free option. Its official Linux installer can install Docs, Community Server, Control Panel, and Talk; the Mail Server can be added separately. This procedure uses the vendor’s Docker-based script on an amd64 Ubuntu server. ONLYOFFICE’s current requirements describe compatible 64-bit Linux distributions rather than explicitly naming Ubuntu 24.04, so confirm compatibility for your own deployment and check the current vendor documentation before production use.
Do not choose this setup for a small virtual machine that falls below the published minimums. ONLYOFFICE lists 4 CPU cores, 8 GB RAM, and 40 GB of free disk space as minimums, with 6 cores and 12 GB RAM recommended. The installer creates a 6 GB swap file automatically. Allow extra disk capacity for uploaded files, logs, backups, and future growth; 40 GB is the listed minimum, not a sizing recommendation for a busy team.
If another web server or application already uses a required port, stop and plan the port or reverse-proxy arrangement before installing. Do not terminate an existing service blindly. For a public server, prepare a domain name and HTTPS plan before inviting users or exposing the portal to the internet.
Connect to the Ubuntu server over SSH, then download the script from ONLYOFFICE’s documented download host:
curl -O https://download.onlyoffice.com/install/workspace-install.shBefore running a privileged installer, confirm that the file arrived and inspect its opening lines:
ls -lh workspace-install.sh
less workspace-install.shPress q to leave the viewer. The vendor’s installation guide is the source for this script and its parameters; use that page to review any changes before repeating the procedure later.
Start the installer with administrator privileges and the documented option to skip Mail:
sudo bash workspace-install.sh -ims falseThe -ims false parameter tells the installer not to install ONLYOFFICE Mail. The script installs and configures the Workspace components using Docker, and may install or update Docker when necessary. Follow any prompts shown by the script. Keep the SSH session open while installation is running and avoid interrupting package or container setup.
If you do want Mail, do not simply remove the parameter and assume email will work automatically. The vendor’s Mail instructions require a valid domain configured for the machine, including appropriate DNS records. Mail also adds services and network ports that you may not need for document collaboration.
When the installer finishes, open a browser on a computer that can reach the server and enter the server’s LAN IP address, such as http://192.168.1.20. Replace that example with the actual address. ONLYOFFICE specifically advises using the machine’s network IP rather than localhost or 127.0.0.1 when checking the installation. Complete the first-run screen presented by your installation and create an administrator account; do not rely on a default password unless the official instructions for your exact version explicitly provide one.
For a remote or internet-facing deployment, configure a DNS name and HTTPS before normal use. The installer’s local-IP check confirms that the service responds on the network; it does not by itself establish secure public access. Follow the official HTTPS procedure for the installation type you chose, and permit only the ports needed for the selected Workspace modules.
Confirm that the installer completed without a fatal error, the portal opens from another device using the server’s LAN IP, and you can finish the initial administrator setup. Then review the firewall and HTTPS configuration before adding users or sharing files. Keep a separate backup plan for Workspace data; a running Docker container is not a backup.
Install ONLYOFFICE Workspace Community on Ubuntu 24.04 with the official Docker script, check server requirements, skip Mail if needed, and verify the portal safely.
Configure matching JWT secrets for ONLYOFFICE Docs and its connector, with safe steps for Linux packages, Docker deployments, and verification.
Configure HAProxy HTTPS, forwarding headers, WebSocket timeouts, and health checks for ONLYOFFICE Docs, then verify editing and saves.
Give an embedded ONLYOFFICE Docs editor your company logo and interface colors with a custom theme file and editor configuration. See edition limits and deployment checks.
Track edits in Writer, preserve an editable ODT source, and check the exported DOCX in Word before sharing it.
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
