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: Document Server, Community Server or Mail Server and follow the instructions on the appropriate page.
Q:What system do I need to have to install the server solution and successfully use it?
A:The system requirements are:
dual core 2 GHz or better
4 GB or more
at least 2 GB of free space
at least 2 GB of swap
amd64 Linux distribution with kernel version 3.10 or later
- Docker: version 1.10 or later
Q:I installed one of the servers using Docker service, but it lacks performance. I am sure that my computer meets all the requirements. 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. It stalls the performance due to the DNS server inaccessibility if no Internet connection is present. So if your Community Server, Document Server or Mail Server 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:
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
addresses with the real IP addresses.
One Click Installation issues
Q:I have authentication problems and cannot connect to the server. What can be done?
A:Check your server configuration. The reason might be that your Linux server have been configured to disallow SSH login via password. Open the
/etc/ssh/sshd_config file using any available editor and look for the following line to find out what the configuration is set for authentication via password:
Change its value to yes
and restart the SSHD service with the following command:
service sshd restart
You will also need to change another line to be able to connect the server using the license key file:
Change its value to yes
and restart the SSHD service as shown above.
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:I cannot run Docker-based server as it crashes for my system. What can be wrong?
A:Docker-based online office server installation requires the presence of mono (version 4.0.0 or later) that may cause problems for some Linux kernel versions. The full list of supported kernel versions is available here).
Document Server usage issues
Q:Data loss has occured when stopping Document Server. How to prevent data loss?
A:Due to the operational characteristic, Document Server 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 Document Server users when you need to stop Document Server in cases of the application update, server reboot etc. To do that, execute the following script on the server where Document Server is installed:
sudo docker exec <CONTAINER> documentserver-prepare4shutdown.sh
Executing the script may take a long time (up to 5 minutes).
Disconnecting users may take a long time (up to 5 minutes).