Install ONLYOFFICE on a Nextcloud Server

  • 1,978 views. Added .

Here's a step-by-step tutorial for installing ONLYOFFICE Community Edition alongside an existing Nextcloud installation! You can copy/paste the commands in this video from here: https://nerdonthestreet.com/wiki?find=Install+ONLYOFFICE+for+Nextcloud

Need a server? Get one at https://digitalocean.nots.co or https://linode.nots.co. Need a domain name? Get one at https://hover.nots.co.

Comments (log in to post)

Great video.
Please how can I solve the onlyoffice 25 concurrent connections limitation?
Thanks
Dear Jacob, I tried to follow your guide to integrate onlyoffice on a debian 10  with nextcloud previously installed and  working with the postgresql database.  The only command that I had problem was this one:  npm install; then I restored the folder that I had previously moved (mv node_modules_old node_modules). At the end of command describe in your tutorial  I have checked both nextcloud and onlyoffice link and both work properly  in https but if i try to set onlyoffice ( Settings -> Administration) I can't find the onlyoffice entry.
Please could you help me to solve this problem? Thank you very much for your attention. Maurizio
I solve the problem, I had forgotten to activate the app.
Thanks for the video! I've installed this a coupe of times on my Debian 10 machine. No issues following this guide. Have you had any issues upgrading the onlyoffice-documentserver?
I don't have ONLYOFFICE installed on any of the servers I'm managing right now. I would not expect any trouble upgrading. With Collabora, the only trouble I run into is if a package upgrade overwrites one of the configuration files I've modified, but apt/dpkg warn me about that so I can take care of it during the upgrade.
Thanks Jacob!  This is a very thorough and excellent tutorial!  This is a game changer and I just totally dropped Google office today.

I’ve been a long time Nextcloud user and previously Owncloud.  I have a Intel Nuc running Ubuntu 18.04 with version 16.08 Nextcloud.

For those using Ubuntu instead of Debian, I thought that I would post a few tips showing the differences:

STEP 0:  This may be obvious to most, but all these steps must be run as superuser.  To help you NOOBS out there, run this command first to be a superuser:   sudo su –

STEP 3:  No need to change this command even though it points to a Debian release of OnlyOffice.  The correct version is automatically downloaded from the Ubuntu repository.

STEP 7:  The install does not fail as noted in the video. The Ubuntu version does not show errors.  However, still proceed to step 8.

STEP 8:  The file is not in the “sites-enabled” directory.  It can be found in the “sites-available” directory.  Do not move the file.  I moved the file and then completed the install.  Everything worked until I powered down my server and restarted.  Nginx did not restart since the file was not in the expected location.  It took me a while to figure out why Nginx didn’t start.  So keep the file in its original directlory. The new command is:

nano /etc/nginx/sites-available/default

I still ran the command “dpkg –configure –a”,but since step 7 didn’t fail, the command seems unnecessary.

STEP 9:  My version of Nextcloud had a different conf file name so the command is slightly different:

cp /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/onlyoffice.conf

Step 11:  The spellchecker works fine for the Ubuntu version.  You can skip this step.

Et Voila!  You’re finished.

Also, don’t forget to update your DDclient.conf file to update your new subdomain IP address for only office.  Otherwise, if your ISP changes your IP address, your OnlyOffice subdomain will not be available.
Glad to hear this was useful to you! It makes sense that Ubuntu would have less hiccups, since it probably gets tested more by the ONLYOFFICE developers. "dpkg –configure -a" will return without giving any output if all of the packages on your system are properly configured.

For anyone else reading, the "DDclient.conf" file you're mentioning is a configuration file for a client used to update dynamic DNS services. Anyone with a static IP address wouldn't need to worry about that. I've considered using a dynamic DNS service to host a server in my apartment, and I might be doing that by now if I was still in my previous apartment, but my current one's a little too small to have another 24/7 machine running.