How To Install OnlyOffice on CentOS Stream 10

ONLYOFFICE stands as a powerful alternative to proprietary office suites, offering an open-source solution for document editing, collaboration, and productivity enhancement. Installing ONLYOFFICE on CentOS Stream 10 provides organizations and individuals with a robust platform for document management and team collaboration. This comprehensive guide walks through the entire installation process, from preparing your CentOS Stream 10 environment to troubleshooting common issues that may arise during setup or operation. By following these detailed instructions, you’ll be able to deploy a fully functional ONLYOFFICE installation tailored to your specific needs and requirements.

Understanding ONLYOFFICE

ONLYOFFICE is a comprehensive open-source office suite designed for collaborative document management and editing. Initially developed in 2009, ONLYOFFICE has evolved into a feature-rich platform that offers an alternative to proprietary solutions like Microsoft Office. The suite consists of several key components, with the Document Server being the core element that enables document editing capabilities. ONLYOFFICE supports various document formats, including DOCX, XLSX, PPTX, and PDF, ensuring compatibility with widely used standards.

The ONLYOFFICE ecosystem offers different editions to meet various user requirements. The Community Edition provides free access to essential features, making it suitable for individual users and small teams. The Enterprise Edition includes additional functionality for larger organizations, while the Developer Edition caters to those looking to integrate ONLYOFFICE into their own software solutions. One of ONLYOFFICE’s standout features is its collaborative editing capability, allowing multiple users to work on documents simultaneously with Fast and Strict co-editing modes.

When compared to other office suites, ONLYOFFICE distinguishes itself through its high level of compatibility with Microsoft Office formats and its robust collaboration tools. The platform’s integration capabilities extend to various content management systems and file-sharing platforms, including Nextcloud, Seafile, ownCloud, WordPress, and SharePoint, making it a versatile solution for diverse organizational needs. By installing ONLYOFFICE on CentOS Stream 10, users gain access to a self-hosted office solution that provides control over data and customization options not available with cloud-based alternatives.

System Requirements for ONLYOFFICE on CentOS Stream 10

Before beginning the installation process, ensuring your system meets the necessary hardware and software requirements is crucial for optimal performance. ONLYOFFICE Document Server demands specific hardware configurations to function efficiently. Your server should have at minimum a dual-core processor with a clock speed of 2 GHz or higher to handle document processing tasks effectively. Memory requirements start at 2 GB of RAM, though 4 GB or more is strongly recommended for smoother operation, especially when dealing with multiple simultaneous users or complex documents.

Storage considerations are equally important, with at least 40 GB of free disk space needed for the application, its dependencies, and document storage. Additionally, configuring a swap space of at least 4 GB is essential to prevent memory-related issues during peak usage periods. These hardware specifications represent the bare minimum requirements; for production environments or larger deployments, consider scaling these resources accordingly to maintain performance under increased load.

Network configuration plays a significant role in ONLYOFFICE deployment, particularly for collaborative features. Ensure your server has a stable internet connection if external access is required. CentOS Stream 10 offers an excellent platform for ONLYOFFICE due to its stability and long-term support characteristics. The installation will require several dependencies, including PostgreSQL (version 12.9 or higher), NGINX (version 1.3.13 or higher), Redis for caching, and RabbitMQ for message queuing. These components work together to provide the foundation for ONLYOFFICE’s document processing and collaboration functionality.

Preparing Your CentOS Stream 10 Environment

Thorough preparation of your CentOS Stream 10 system creates a solid foundation for a successful ONLYOFFICE installation. Begin by updating your system packages to ensure you’re working with the latest software versions and security patches. This minimizes compatibility issues and potential security vulnerabilities during the installation process. Execute the following command to update your system:

sudo dnf update -y

Next, install the EPEL (Extra Packages for Enterprise Linux) repository, which provides additional packages necessary for ONLYOFFICE installation. The EPEL repository contains many open-source packages that are not included in the default CentOS repositories but are required dependencies for ONLYOFFICE:

sudo dnf install -y epel-release

SELinux configuration requires special attention when installing ONLYOFFICE. While SELinux enhances security, it can sometimes interfere with the proper functioning of applications like ONLYOFFICE. For a trouble-free installation, you can temporarily disable SELinux by editing its configuration file:

sudo nano /etc/selinux/config

Change the SELINUX line to read:

SELINUX=disabled

Save the file and reboot your system for the changes to take effect. Alternatively, if disabling SELinux entirely is not acceptable for your security policy, you could configure it properly to allow ONLYOFFICE operations while maintaining protection.

Firewall configuration is another critical step in preparing your environment. You’ll need to open specific ports to allow communication with the ONLYOFFICE server. For standard HTTP and HTTPS access, open ports 80 and 443 respectively:

sudo firewall-cmd --permanent --add-service=http sudo firewall-cmd --permanent --add-service=https sudo firewall-cmd --reload

Setting up adequate swap space ensures system stability during resource-intensive operations. If your system lacks sufficient swap space, create or expand it using these commands:

sudo dd if=/dev/zero of=/swapfile bs=1M count=4096 sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile

To make this swap file permanent, add it to /etc/fstab:

echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

Proper time synchronization is essential for collaborative features and certificate validation. Install and configure the chrony service:

sudo dnf install -y chrony sudo systemctl enable chronyd sudo systemctl start chronyd

Finally, install basic utilities and development tools that will be necessary for compiling certain components during the installation process:

sudo dnf install -y nano wget curl git make gcc gcc-c++ kernel-devel

These preparation steps create an optimized environment for ONLYOFFICE installation, reducing the likelihood of issues during subsequent stages of the setup process.

Installing Core Dependencies

ONLYOFFICE relies on several core dependencies to function properly. Installing and configuring these components correctly is essential for a successful deployment. Let’s begin with PostgreSQL, which serves as the database backend for ONLYOFFICE Document Server.

PostgreSQL Installation and Configuration

PostgreSQL stores all document-related data and user information. Install PostgreSQL using the following commands:

sudo dnf install -y postgresql-server postgresql-contrib sudo postgresql-setup --initdb sudo systemctl enable postgresql sudo systemctl start postgresql

After installation, create a dedicated database and user for ONLYOFFICE:

sudo -u postgres psql -c "CREATE DATABASE onlyoffice;" sudo -u postgres psql -c "CREATE USER onlyoffice WITH PASSWORD 'your_secure_password';" sudo -u postgres psql -c "GRANT ALL PRIVILEGES ON DATABASE onlyoffice TO onlyoffice;"

Enhance the security of your PostgreSQL installation by editing the pg_hba.conf file to use MD5 authentication:

sudo nano /var/lib/pgsql/data/pg_hba.conf

Change the authentication methods to “md5” for local connections, then restart PostgreSQL to apply the changes:

sudo systemctl restart postgresql

NGINX Installation and Setup

NGINX serves as the web server and reverse proxy for ONLYOFFICE. Install NGINX by first adding its repository:

sudo tee /etc/yum.repos.d/nginx.repo << EOF [nginx-stable] name=nginx stable repo baseurl=http://nginx.org/packages/centos/\$releasever/\$basearch/ gpgcheck=1 enabled=1 gpgkey=https://nginx.org/keys/nginx_signing.key module_hotfixes=true EOF sudo dnf install -y nginx sudo systemctl enable nginx sudo systemctl start nginx

The basic NGINX configuration will be modified later to accommodate ONLYOFFICE’s specific requirements. For now, verify that NGINX is running correctly:

sudo systemctl status nginx

Redis Installation and Configuration

Redis provides caching and session storage for ONLYOFFICE, improving performance and enabling real-time collaboration features. Install Redis with these commands:

sudo dnf install -y redis sudo systemctl enable redis sudo systemctl start redis

Verify Redis is running properly:

sudo systemctl status redis

RabbitMQ Installation and Setup

RabbitMQ handles message queuing for various ONLYOFFICE components, facilitating communication between different parts of the system. Install RabbitMQ by first adding the Erlang repository, which is required for RabbitMQ:

sudo dnf install -y https://github.com/rabbitmq/erlang-rpm/releases/download/v23.3.4.11/erlang-23.3.4.11-1.el8.x86_64.rpm

Then add the RabbitMQ repository and install it:

sudo rpm --import https://github.com/rabbitmq/signing-keys/releases/download/2.0/rabbitmq-release-signing-key.asc sudo rpm -Uvh https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.9.13/rabbitmq-server-3.9.13-1.el8.noarch.rpm sudo dnf install -y rabbitmq-server sudo systemctl enable rabbitmq-server sudo systemctl start rabbitmq-server

Verify RabbitMQ is running correctly:

sudo systemctl status rabbitmq-server

These core dependencies provide the foundation for ONLYOFFICE functionality, handling data storage, web access, caching, and message queuing respectively. Proper installation and configuration of these components is crucial for ensuring optimal performance and reliability of your ONLYOFFICE deployment on CentOS Stream 10.

Installing Microsoft Core Fonts

Microsoft Core Fonts play a crucial role in ensuring document compatibility and proper rendering in ONLYOFFICE. These fonts enable ONLYOFFICE to maintain visual consistency with documents created in Microsoft Office and other applications. Without these fonts, documents may display incorrectly, with text layout issues or font substitutions that alter the intended appearance of your content.

Begin by installing the necessary packages for handling Microsoft font formats:

sudo dnf install -y cabextract fontconfig xorg-x11-font-utils

The cabextract utility is essential for extracting Microsoft Cabinet (.cab) files that contain the fonts, while fontconfig and xorg-x11-font-utils provide the required font management capabilities.

Next, download and install the msttcore fonts using a convenient installation script:

sudo rpm -i https://downloads.sourceforge.net/project/mscorefonts2/rpms/msttcore-fonts-installer-2.6-1.noarch.rpm

This script automatically downloads and installs common Microsoft fonts including Arial, Times New Roman, Verdana, and others that are frequently used in office documents. The installation process may take a few minutes as it downloads the fonts from Microsoft’s servers.

After installation, update the font cache to make the new fonts available to the system:

sudo fc-cache -v

To verify that the fonts were installed correctly, you can list the available fonts:

fc-list | grep -i "arial\|times\|verdana"

If the installation was successful, you should see the Microsoft fonts listed in the output. These fonts will ensure that documents displayed and edited in ONLYOFFICE maintain their intended formatting and appearance, providing a seamless experience when working with files created in other office suites.

Should you encounter any font-related issues after installation, such as missing characters or incorrect rendering, try rebuilding the font cache completely:

sudo fc-cache -f -v

This forces a full rebuild of the font cache, which can resolve most font detection problems. With Microsoft Core Fonts properly installed, your ONLYOFFICE installation will be better equipped to handle a wide range of document formats with consistent and accurate rendering.

Method 1: Installing ONLYOFFICE via RPM Packages

Installing ONLYOFFICE via RPM packages offers a straightforward approach that integrates well with CentOS Stream 10’s package management system. This method provides a native installation experience and simplifies future updates through standard system tools. Begin by adding the official ONLYOFFICE repository to your system, which ensures you receive the correct packages designed for your distribution:

sudo tee /etc/yum.repos.d/onlyoffice.repo << EOF [onlyoffice] name=ONLYOFFICE Repository baseurl=https://download.onlyoffice.com/repo/centos/main/noarch/ gpgcheck=1 enabled=1 gpgkey=https://download.onlyoffice.com/GPG-KEY-ONLYOFFICE EOF

After adding the repository, import the GPG key used for package verification. This step is critical for security as it ensures the authenticity of the packages you’re installing:

sudo rpm --import https://download.onlyoffice.com/GPG-KEY-ONLYOFFICE

Now you’re ready to install the ONLYOFFICE Document Server package. The following command will download and install ONLYOFFICE along with any dependencies that weren’t installed during the previous steps:

sudo dnf install -y onlyoffice-documentserver

The installation process may take several minutes depending on your internet connection speed and system performance. During installation, the package manager handles dependency resolution automatically, ensuring all required components are installed and properly configured.

As the installation progresses, you might see various configuration prompts. In most cases, accepting the default options is appropriate unless you have specific requirements for your environment. The package installation also includes automatic configuration of previously installed components like NGINX and PostgreSQL to work with ONLYOFFICE.

After installation completes, verify that the Document Server is functioning properly by checking its status:

sudo systemctl status ds-converter
sudo systemctl status ds-docservice

These commands check the status of key ONLYOFFICE services that handle document conversion and processing. If these services are active and running, your installation has been successful.

If you encounter any issues during installation, such as dependency conflicts or package unavailability, check the error messages carefully. Common solutions include ensuring your system is fully updated, verifying that all repositories are enabled, and confirming that your system meets the minimum requirements. The installation logs, located at /var/log/onlyoffice, can provide valuable information for troubleshooting installation problems.

The RPM installation method creates a standard system service configuration, making it easy to manage ONLYOFFICE using familiar tools like systemctl. This approach is particularly suitable for administrators who prefer traditional Linux service management and want tight integration with the system’s package management tools.

Method 2: Installing ONLYOFFICE via Docker

Docker installation provides an encapsulated and consistent environment for ONLYOFFICE, making it an excellent choice for many deployment scenarios. This method isolates the application from the host system, simplifying deployment and maintenance while ensuring consistency across different environments. Begin by installing Docker on your CentOS Stream 10 system if it’s not already installed:

sudo dnf install -y dnf-plugins-core sudo dnf config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo sudo dnf install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin sudo systemctl enable docker sudo systemctl start docker

Verify Docker is running correctly:

sudo docker run hello-world

With Docker properly installed, you can now pull the ONLYOFFICE Document Server image from Docker Hub. This image contains a pre-configured ONLYOFFICE installation with all necessary dependencies:

sudo docker pull onlyoffice/documentserver

The image download might take some time depending on your internet connection speed. After downloading, create persistent volume mappings to ensure your data remains intact even if the container is removed or updated:

sudo mkdir -p /app/onlyoffice/DocumentServer/data sudo mkdir -p /app/onlyoffice/DocumentServer/logs sudo mkdir -p /app/onlyoffice/DocumentServer/lib sudo mkdir -p /app/onlyoffice/DocumentServer/db

Now run the ONLYOFFICE Docker container with appropriate volume mappings and port configurations:

sudo docker run -i -t -d -p 80:80 \ -v /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data \ -v /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice \ -v /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice \ -v /app/onlyoffice/DocumentServer/db:/var/lib/postgresql \ --restart=always \ --name onlyoffice-document-server \ onlyoffice/documentserver

This command runs the container in detached mode (-d), maps container port 80 to host port 80, creates persistent volume mappings, sets the container to restart automatically if it stops, and assigns a name to the container for easier management.

For more complex deployments, Docker Compose provides a convenient way to manage multi-container applications. Create a docker-compose.yml file:

sudo nano docker-compose.yml

Add the following content to the file:

version: '3' services: onlyoffice-document-server: container_name: onlyoffice-document-server image: onlyoffice/documentserver ports: - "80:80" volumes: - /app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data - /app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice - /app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice - /app/onlyoffice/DocumentServer/db:/var/lib/postgresql restart: always

Start the container using Docker Compose:

sudo docker-compose up -d

The Docker installation method simplifies maintenance tasks like updates and backups. To update ONLYOFFICE, simply pull the latest image and restart the container:

sudo docker pull onlyoffice/documentserver sudo docker stop onlyoffice-document-server sudo docker rm onlyoffice-document-server # Run the docker run command again with the same parameters

For Docker Compose deployments, the update process is even simpler:

sudo docker-compose pull sudo docker-compose down sudo docker-compose up -d

Docker’s containerized approach offers advantages in resource isolation, deployment consistency, and simplified management, making it an increasingly popular choice for deploying applications like ONLYOFFICE on CentOS Stream 10.

Post-Installation Configuration

After successfully installing ONLYOFFICE Document Server, proper configuration ensures optimal performance, security, and functionality. Begin by running the documentserver-configure.sh script, which sets up essential components and verifies the installation:

sudo /usr/bin/documentserver-configure.sh

This script performs various configuration tasks, including database initialization, service configuration, and permission settings. Follow the prompts carefully, providing any requested information such as database credentials created earlier.

Database connection configuration is a critical aspect of post-installation setup. If you need to modify the database settings after initial configuration, edit the connection parameters in the configuration file:

sudo nano /etc/onlyoffice/documentserver/local.json

In this file, locate the “dbType” and “connectionString” parameters and adjust them according to your PostgreSQL setup. After making changes, restart the ONLYOFFICE services:

sudo systemctl restart ds-converter
sudo systemctl restart ds-docservice

RabbitMQ and Redis connection configuration might also require adjustment depending on your specific environment. These settings can be modified in the same local.json file. Look for the “rabbitmq” and “redis” sections and update the connection parameters if necessary.

NGINX configuration for ONLYOFFICE involves setting up proper server blocks and proxy settings. The default configuration works for basic installations, but you might want to customize it for specific requirements:

sudo nano /etc/nginx/conf.d/onlyoffice-documentserver.conf

In this file, you can adjust various NGINX settings such as server_name, SSL configuration, and proxy parameters. After making changes, test the NGINX configuration and reload it:

sudo nginx -t sudo systemctl reload nginx

If you need to change the default port (80) that ONLYOFFICE listens on, modify the NGINX configuration file to use a different port:

server { listen 8080; # Other settings remain the same # ... }

Setting up document examples helps verify that the installation is working correctly. ONLYOFFICE provides sample documents that you can use for testing:

sudo cp -r /usr/share/onlyoffice/documentserver-example/documents /var/www/onlyoffice/Data/ sudo chown -R onlyoffice:onlyoffice /var/www/onlyoffice/Data/documents

Test the installation by navigating to http://your-server-ip in a web browser. You should see the ONLYOFFICE welcome page. If you’ve set up a different port, include it in the URL (e.g., http://your-server-ip:8080).

These post-installation configuration steps ensure that your ONLYOFFICE Document Server is properly set up and ready for use. Take time to understand each configuration option and adjust them according to your specific requirements for an optimized deployment.

Securing Your ONLYOFFICE Installation

Implementing robust security measures for your ONLYOFFICE installation is crucial to protect sensitive documents and user data. Start by setting up SSL/TLS encryption to secure data transmission between users and the server. Let’s Encrypt provides free SSL certificates that can be easily implemented:

sudo dnf install -y certbot python3-certbot-nginx
sudo certbot --nginx -d your-domain.com

Follow the certbot prompts to obtain and install certificates. This process automatically configures NGINX to use HTTPS. If you’re using a self-signed certificate instead, generate it with:

sudo mkdir -p /etc/ssl/onlyoffice sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/ssl/onlyoffice/onlyoffice.key -out /etc/ssl/onlyoffice/onlyoffice.crt

Then update your NGINX configuration to use these certificates:

sudo nano /etc/nginx/conf.d/onlyoffice-documentserver.conf

Add the SSL configuration:

server { listen 443 ssl; server_name your-domain.com; ssl_certificate /etc/ssl/onlyoffice/onlyoffice.crt; ssl_certificate_key /etc/ssl/onlyoffice/onlyoffice.key; # Other SSL settings ssl_protocols TLSv1.2 TLSv1.3; ssl_prefer_server_ciphers on; ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH"; # Existing configuration follows # ... }

Configure firewall rules to restrict access to necessary ports only. CentOS Stream 10 uses firewalld for firewall management:

sudo firewall-cmd --permanent --add-service=https sudo firewall-cmd --permanent --remove-service=http # Optional: remove HTTP if using HTTPS only sudo firewall-cmd --reload

User authentication setup is essential for controlling access to your ONLYOFFICE installation. Edit the JWT configuration to enable secure authentication:

sudo nano /etc/onlyoffice/documentserver/local.json

In the “services” section, update the JWT settings:

"CoAuthoring": { "token": { "enable": true, "secret": "your-secure-random-string", "authorizationHeader": "Authorization" } }

Document access control can be implemented through JWT token parameters that specify access rights for different users. This allows granular control over who can view, edit, or comment on documents.

Implement regular update procedures to ensure your ONLYOFFICE installation receives security patches promptly:

# For RPM installation
sudo dnf update -y onlyoffice-documentserver
# For Docker installation sudo docker pull onlyoffice/documentserver
sudo docker stop onlyoffice-document-server
sudo docker rm onlyoffice-document-server
# Run the docker run command again with the same parameters

Finally, establish backup strategies for your ONLYOFFICE data to prevent loss in case of system failure:

# For RPM installation
sudo mkdir -p /backup/onlyoffice sudo
cp -r /var/www/onlyoffice/Data /backup/onlyoffice/ 
sudo pg_dump -U postgres onlyoffice > /backup/onlyoffice/database_backup.sql
# For Docker installation
sudo cp -r /app/onlyoffice /backup/

These security measures collectively protect your ONLYOFFICE installation from unauthorized access and data loss, ensuring a secure environment for document collaboration and management.

Integrating ONLYOFFICE with Other Platforms

ONLYOFFICE Document Server’s true potential is realized when integrated with other platforms, creating a comprehensive document management ecosystem. The server offers extensive integration capabilities with popular file-sharing and collaboration platforms. Nextcloud integration is particularly popular due to its robust file-sharing capabilities. To connect ONLYOFFICE with Nextcloud, install the ONLYOFFICE Nextcloud app from the Nextcloud App Store, then configure it to point to your Document Server:

Document Editing Service address: https://your-onlyoffice-server.com/ Document Editing Service address for internal requests from the server: https://your-onlyoffice-server.com/
Server address for internal requests from ONLYOFFICE Document Server: https://your-nextcloud-server.com/

Similarly, ONLYOFFICE can be integrated with ownCloud through its marketplace app. After installing the app, configure it with your Document Server address and JWT secret key for secure communication. This integration enables ownCloud users to edit documents directly within the ownCloud interface using ONLYOFFICE’s editing capabilities.

For SharePoint integration, ONLYOFFICE provides specific connectors that enable document editing within SharePoint environments. This integration is particularly valuable for organizations that use SharePoint as their primary document management system but want ONLYOFFICE’s collaborative editing features.

WordPress websites can benefit from ONLYOFFICE integration through the ONLYOFFICE WordPress plugin, which allows embedding document editors into WordPress pages and posts. This is useful for creating interactive content or collaborative editing environments within a WordPress site.

For custom integrations, ONLYOFFICE provides a comprehensive API that allows developers to integrate the Document Server with proprietary applications or services. The API documentation is available on the ONLYOFFICE website and includes examples for various programming languages. Basic API usage involves generating JWT tokens for authentication and making REST API calls to the Document Server to perform operations like opening, editing, and saving documents.

These integration capabilities extend ONLYOFFICE’s functionality beyond standalone document editing, creating interconnected systems where documents can flow seamlessly between different platforms while maintaining editing capabilities and version control.

Troubleshooting Common Issues

Even with careful installation and configuration, issues may arise with your ONLYOFFICE deployment. Understanding common problems and their solutions can save considerable time and frustration. Connection and access problems frequently occur after initial setup. If you can’t access the ONLYOFFICE interface, first verify that the services are running:

sudo systemctl status ds-converter
sudo systemctl status ds-docservice
sudo systemctl status nginx

If any service is not running, start it and check for errors in the logs:

sudo systemctl start ds-converter
sudo systemctl start ds-docservice
sudo journalctl -u ds-converter
journalctl -u ds-docservice

Network connectivity issues might be caused by firewall configurations. Verify that the required ports are open:

sudo firewall-cmd --list-all

Document conversion issues often stem from missing dependencies or configuration problems. Check the converter service logs for specific errors:

sudo tail -f /var/log/onlyoffice/documentserver/converter/err.log

Common conversion problems include missing fonts or PDF libraries. Ensure all required packages are installed:

sudo dnf install -y fontconfig libreoffice ghostscript

Performance optimization becomes necessary as user load increases. Monitor system resources to identify bottlenecks:

top free -m df -h

If CPU usage is consistently high, consider increasing the number of available workers in the ONLYOFFICE configuration:

sudo nano /etc/onlyoffice/documentserver/local.json

In the “services.CoAuthoring.server.maxWorkers” section, increase the value based on your available CPU cores.

Log file analysis provides valuable insights into issues that aren’t immediately apparent. ONLYOFFICE logs are located in various directories:

# Main logs /var/log/onlyoffice/documentserver/ # Specific component logs /var/log/onlyoffice/documentserver/converter/ /var/log/onlyoffice/documentserver/docservice/ /var/log/onlyoffice/documentserver/web/

Database troubleshooting may be necessary if document operations fail. Check PostgreSQL connectivity and permissions:

sudo -u postgres psql -c "SELECT current_database();" sudo -u postgres psql -c "SELECT has_database_privilege('onlyoffice', 'onlyoffice', 'CONNECT');"

For persistent issues, the ONLYOFFICE community forums provide an excellent resource where experienced users and developers can offer assistance based on their own experiences. The official documentation also contains troubleshooting sections for specific components and scenarios.

Congratulations! You have successfully installed OnlyOffice. Thanks for using this tutorial for installing the OnlyOffice on CentOS Stream 10 system. For additional help or useful information, we recommend you check the OnlyOffice website.