Q:I want to install the Docker-based server onto my local server. How can I do that?

A:The latest Docker-based online office server is available at Docker hub. Please select which you would like to install: ONLYOFFICE Docs, ONLYOFFICE Groups or ONLYOFFICE Mail and follow the instructions on the appropriate page.

Q:After I create and enter the portal, I can see an unknown user in the People module with the 'fake user' name. There is also some OnlyofficeHealthCheck service in the services list. Why is this and do I need to do something about it?

A:The user and the service are a part of the upcoming Health Check functionality which will be available for the portals in the future releases. As for now it is not functional, so you can either leave it as is or disable the OnlyofficeHealthCheck service and remove it from the service automatic startup list.

Q:What system do I need to have to install the server solution and successfully use it?

A:The system requirements are:

• CPU
  dual core 2 GHz or better
• RAM
  4 GB or more
• HDD
  at least 20 GB of free space
• SWAP
  at least 4 GB, but depends of the host OS. More is better
• OS
  amd64 Linux distribution with kernel version 3.10 or later
• Additional requirements
  • Docker: any version supported by Docker team

Q:I installed one of the server versions using the Docker service, but I have some issues related to the DNS server or own name resolution. What can be wrong?

A:Docker specifies Google DNS servers by default and the server tries to contact them every time it makes some network requests. If your ONLYOFFICE Groups, ONLYOFFICE Docs or ONLYOFFICE Mail is not going to have access to the Internet, we recommend that you change the default Docker DNS address to the address of your local DNS server. To do that go to the /etc/default/docker file and change the IP address in the following line to the IP address of a DNS server in your local network:

docker_OPTS="--dns 8.8.8.8"

For the RPM based operating systems like CentOS, the configuration file can be located here: /etc/docker/daemon.json

Q:The document editors open and the interface appears, but the document itself does not load, continually showing loading progress. What can be done?

A:The reason might be that the computer must be able to address itself using the Internet loopback access, i.e. it must be accessible from outside for itself. You can allow it to do that editing the iptables to have the redirects like this:

iptables -t nat -A PREROUTING -d <public_ip> -j DNAT --to-destination <local_ip>
iptables -t nat -A POSTROUTING -s <local_ip> -j SNAT --to-source <piblic_ip>

Do not forget to substitute the public_ip and the local_ip addresses with the real IP addresses.

Q:I added a custom interface theme or updated my editor language files (corrected some translations) but the server still shows the previous values instead of the correct ones. How can I reset the cache for all the users at the same time?

A:Please follow the steps to reset the cache:
Find the /etc/nginx/includes/ds-docservice.conf and /etc/nginx/includes/ds-spellchecker.conf files. There must be the build date and time value. Change these values to some other (any value will do, but the main thing that it must be the same in all the places), and restart NGINX:

sudo service nginx reload

The cache should be reset for all the server users.

Q:I addedd a self-signed SSL certificate and now I have the error when opening the SSO metadata page, when working with WebDAV and other node.js services. What can be done to fix that?

A:If you encounter an issue with obtaining the SSO metadata, WebDAV and other node.js services when using self-signed SSL certificates, you can try one of the following options for resolving this issue:

Option 1 - Add parameters for the service launch.

1. Open the onlyofficeSsoAuth.service file (within the CommunityServer container):

   nano /lib/systemd/system/onlyofficeSsoAuth.service

2. Add the following string specifying the path to the root certificate at the end of the [Service] block:

   Environment=NODE_EXTRA_CA_CERTS=/etc/rootCA.pem

3. Restart services:

   systemctl daemon-reload
   systemctl restart onlyofficeSsoAuth

Option 2 - Use the system bundle of certificates.

1. Open the onlyofficeSsoAuth.service file (within the CommunityServer container):

   nano /lib/systemd/system/onlyofficeSsoAuth.service

2. Find the following string in the [Service] block:

   ExecStart=/usr/bin/node /var/www/onlyoffice/Services/ASC.SsoAuth/app.js UNIX.SERVER

   Replace it with the following one:

   ExecStart=/usr/bin/node --use-openssl-ca /var/www/onlyoffice/Services/ASC.SsoAuth/app.js UNIX.SERVER

3. For CentOS, additionally add the following string specifying the path to the bundle of certificates at the end of the [Service] block:

   Environment=SSL_CERT_FILE=/etc/pki/tls/certs/ca-bundle.trust.crt

4. Restart services:

   systemctl daemon-reload
   systemctl restart onlyofficeSsoAuth

Q:I rebooted the server without stopping the docker container with docker stop id command and now I have the ERR_TOO_MANY_REDIRECTS error for my server. What can be done to fix that?

A:Please edit the /var/www/onlyoffice/WebStudio/web.appsettings.config file removing the very last line:

<add key="web.warmup.type" value="basic" />

and restart monoserve with the following command:

sudo service monoserve restart

Q:I'm using Fedora Linux and processes fail to start inside Docker container. Is there a fix to the issue?

A:Fedora and RHEL/CentOS users should try disabling SELinux with setenforce 0 command. If it fixes the issue then you can either stick with SELinux disabled which is not recommended by RedHat, or switch to using Ubuntu.

Q:Data loss has occured when stopping ONLYOFFICE Docs. How to prevent data loss?

A:Due to the operational characteristic, ONLYOFFICE Docs saves a document only after the document has been closed by all the users who edited it. To avoid data loss, you must forcefully disconnect the ONLYOFFICE Docs users when you need to stop ONLYOFFICE Docs in cases of the application update, server reboot etc. To do that, execute the following script on the server where ONLYOFFICE Docs is installed:

sudo docker exec <CONTAINER> documentserver-prepare4shutdown.sh