Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.
Nextcloud and OnlyOffice Integration

Nextcloud and OnlyOffice Integration

An optional Step 7 has been added to this resource. It will ensure the latest version of the OnlyOffice Document Server is always presented to Nextcloud on FreeNAS.
This update brings us one step closer to automatic updating of the OnlyOffice Document Server. Docker Compose is the enabler for this.

Update instructions are provided below for those who have applied the previous update.

1. From a Ubuntu terminal window, remove the OnlyOffice Document Server container sudo docker rm -f onlyoffice-document-server.

2. Remove the OnlyOffice image. First list all images sudo docker images -a, then delete the OnlyOffice image using sudo docker rmi <ImageID>. See the example below.

screenshot.75.jpg

e.g. sudo docker rmi d06214a03e27

Now revisit steps 3 and 4 of this resource.
The OnlyOffice Document Server is the only component of the OnlyOffice Community Server that is required for Nextcloud-OnlyOffice Integration. Steps 4 to 6 of this resource have been revised to reflect this.

Update instructions are provided below for those who have used the original version of this resource. While this step is entirely optional, future releases of this resource wil use Docker Compose for installing and automatically keeping OnlyOffice Document Server current, so if that is of interest to you, please keep on top of the updates.

1. Review and apply the previous resource update (TLS with HTTP validation) if applicable.
2. From a Ubuntu terminal window, remove all OnlyOffice Community Server containers.

Code:
sudo docker rm -f onlyoffice-document-server
sudo docker rm -f onlyoffice-community-server
sudo docker rm -f onlyoffice-mysql-server

3. Now remove the OnlyOffice images. First list them sudo docker images -a, then delete them using sudo docker rmi <ImageID>. See the example below.

screenshot.309.png


e.g. sudo docker rmi d06214a03e27 10cefbc961d5 e9c354083de7

4. Redo steps 4 to 6 of the resource.
Using TLS with HTTP validation rather than TLS with DNS validation for automatic HTTPS simplifies the setup of Caddy. The Caddy examples provided have been revised to reflect this change.

If you're updating from the original version of this resource, the steps are basically as follows:
  1. Save your Caddyfile.
  2. Rebuild the Caddy resource with automatic HTTPS using TLS with HTTP validation.
  3. Make sure you have CNAME records in Cloudflare for both cloud.mydomain.com and office.mydomain.com.
  4. Restore your Caddyfile, but remove the lines below for each code block.
Code:
  tls {
    dns cloudflare
  }
  • Like
Reactions: claudioferraz
Top