ONLYOFFICE¶

In this article:

• ONLYOFFICE. Main Features
• Deployment Features
• Getting Started After Deploying OnlyOffice
• Access to Web Interface
• JWT Secret Configuration
• Enabling Examples for Testing
• Ordering a server with ONLYOFFICE using the API

ONLYOFFICE. Main Features¶

• Real-time Document Editing: Full-featured editors for DOCX, XLSX, PPTX with collaborative editing capabilities;
• Compatibility with Microsoft Office Formats: Complete support for MS Office formats, including complex formatting;
• Collaborative Editing: Simultaneous document editing by multiple users with change tracking;
• Embedded Comments and Chat: Tools for discussing documents directly within the editor interface;
• Version Control: Tracking of changes history with the ability to revert to previous versions;
• Plugins and Integrations: Extending functionality through plugins and integration with popular storage systems;
• Security: Support for JWT tokens to protect API and data encryption during transmission;
• API for Developers: REST API for integrating with custom applications;
• Mobile Support: Adaptive interface for tablets and smartphones.

Deployment Features¶

• Containerized deployment - the system comes with Docker and pre-configured containers for quick setup.
• Key Containers:
  • onlyoffice-docs - main ONLYOFFICE container;
  • nginx-nginx-1 - Nginx web server with SSL support via Certbot (jonasal/nginx-certbot:latest).
• Network Configuration:
  • External Ports: 80 (HTTP), 443 (HTTPS);
  • Internal OnlyOffice Port: 8080 (forwarded to host: 0.0.0.0:8080->80/tcp);
  • Automatic acquisition of SSL certificates through Let's Encrypt.
• Key Directories:
  • /etc/onlyoffice - configuration files for ONLYOFFICE inside the container;
  • /var/lib/onlyoffice - application data;
  • /var/log/onlyoffice - system operation logs;
  • /var/www/onlyoffice - root directory of the web application;
  • /var/www/onlyoffice/documentserver - main Document Server directory.

Getting Started After Deploying ONLYOFFICE¶

After payment for the order to the email specified during registration, a notification about server readiness will be sent. It will include the VPS IP address as well as login and password for connection. Our company's clients manage equipment through the server management panel and API — Invapi.

Authorization data can be found in the Information >> Tags tab of the server control panel or in the sent email:

• Link to access ONLYOFFICE web interface panel: in the webpanel tag;
• Login and Password for managing the server: sent via email upon server delivery.

Access to Web Interface¶

Checking ONLYOFFICE Functionality¶

1. Open a web browser and go to the link from the webpanel tag;

2. You should see the ONLYOFFICE welcome page:

   

3. To check editor functionality, use the built-in examples (see "Enabling Examples for Testing" section).

Checking Service Status¶

To check the status of containers, run the command on the server:

docker ps

CONTAINER ID   IMAGE                          STATUS        PORTS                    NAMES
527cd331a316   jonasal/nginx-certbot:latest   Up 19 hours                           nginx-nginx-1
e32700b1ac75   onlyoffice/documentserver      Up 19 hours   0.0.0.0:8080->80/tcp    onlyoffice-docs

JWT Secret Configuration¶

Viewing Current JWT Secret¶

The JWT secret is used for protecting the Document Server API. To view its current value:

sudo docker exec e32700b1ac75 /var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/local.json 'services.CoAuthoring.secret.session.string'

Structure of JWT Tokens¶

ONLYOFFICE uses three types of JWT secrets for different purposes:

• secret.inbox.string - for incoming requests from external systems to ONLYOFFICE;
• secret.outbox.string - for outgoing requests from ONLYOFFICE to external systems;
• secret.session.string - for internal sessions and interactions between components.

Changing JWT Secrets¶

To change JWT secrets, follow these steps:

1. Create a backup of the configuration:

   docker exec onlyoffice-docs cp /etc/onlyoffice/documentserver/local.json /etc/onlyoffice/documentserver/local.json.backup
   

2. Log into the OnlyOffice container:

   docker exec -it onlyoffice-docs /bin/bash
   

3. Edit the configuration file:

   nano /etc/onlyoffice/documentserver/local.json
   

4. Find the services.CoAuthoring.secret section and change values:

   "secret": {
     "inbox": {
       "string": "your_unique_secret_for_incoming_requests"
     },
     "outbox": {
       "string": "your_unique_secret_for_outgoing_requests"
     },
     "session": {
       "string": "your_unique_secret_for_sessions"
     }
   }
   

5. Save the file and exit the editor (Ctrl+X, then Y, then Enter);
6. Restart the container to apply changes:

   docker restart onlyoffice-docs
   

7. Check that the service started correctly:

   docker logs onlyoffice-docs --tail 100
   

Enabling Examples for Testing¶

ONLYOFFICE includes built-in examples for testing document editors. By default, they are disabled.

Activating Examples¶

To enable test examples, execute the following commands:

Start example service:

sudo docker exec e32700b1ac75 sudo supervisorctl start ds:example

sudo docker exec e32700b1ac75 sudo sed 's,autostart=false,autostart=true,' -i /etc/supervisor/conf.d/ds-example.conf

1. Open in a browser: https://your-domain/welcome/;
2. You will see a page with editor examples;
3. Click on any document type to test:
   • Document - for creating text documents;
   • Spreadsheet - for creating spreadsheets;
   • Presentation - for creating presentations;
   • PDF form - for working with PDF forms.

Ordering a server with ONLYOFFICE using the API¶

To install this software using the API, follow these instructions

Some of the content on this page was created or translated using AI.