NextCloud with OnlyOffice/Community Document Server on AMD plattform?

[KristofferLindberg]

Hi all

I have installed NextCloud 18.0.2 on my FreeNAS 11.3 server and installed the latest OnlyOffice with Community Document Server
When trying to read/create a word/excel/pp document I receive the following error:

Community document server is not supported for this instance, please setup and configure an external document server
only linux based servers are supported

I think I have read somewhere that OnlyOffice might not work on AMD plattform, only Intel platforms, is that really correct or might I have another problem?

Regards
Kristoffer

 

[Basil Hendroff]

only linux based servers are supported

It's a Linux binary that doesn't run directly on FreeBSD. There's some information in the discussion thread at Scripted installation of Nextcloud 18 in iocage jail from this post and then again more recently from this post. It appears there has been a breakthrough of sorts.

 

[Patrick M. Hausen]

You can run a VM with e.g. Ubuntu and run the document server in there.

 

[KristofferLindberg]

ok, thanks for the answers. Seems it was a compability problem then, but with freebsd rather than AMD
I was just curious and wanted to try onlyoffice on my FreeNAS.
I will check out if I want to install a VM or if I wait to see if a freebsd release will be available in the near future then

 

[SKB]

You can run a VM with e.g. Ubuntu and run the document server in there.

Hello,
how is it possible, to run only the document server inside the VM?
What needs to be done there?

 

[Patrick M. Hausen]

Rough sketch - part from memory, part from my live system:

Code:

mkdir -p /app/onlyoffice/DocumentServer
cd /app/onlyoffice/DocumentServer
# place the file docker-compose.yml there
# place the file update.sh there
chmod 755 update.sh
apt install docker.io
apt install docker-compose
docker-compose up

Create a cronjob for root: 0 5 * * * /app/onlyoffice/DocumentServer/update.sh

Done. I leave SSL to a reverse proxy with Apache24 and Dehydrated.

All of this is documented here:

Installation Guides - ONLYOFFICE

ONLYOFFICE Installation Guides.

helpcenter.onlyoffice.com

Thanks to @Basil Hendroff for the first implementation of automatic updates for Docker containers on FreeNAS.

HTH,
Patrick

docker-compose.yml:

Code:

version: '3.3'
services:
  documentserver:
    container_name: onlyoffice
    restart: always
    image: 'onlyoffice/documentserver'
    ports:
      - '80:80'
      - '443:443'
    volumes:
      - '/app/onlyoffice/DocumentServer/logs:/var/log/onlyoffice'
      - '/app/onlyoffice/DocumentServer/data:/var/www/onlyoffice/Data'
      - '/app/onlyoffice/DocumentServer/lib:/var/lib/onlyoffice'
      - '/app/onlyoffice/DocumentServer/db:/var/lib/postgresql'
    environment:
      - JWT_ENABLED=true
      - JWT_SECRET=topsecrettopsecret

update.sh:

Code:

#! /bin/sh

mydir=`dirname "$0"`

cd "${mydir}" || exit 1
exec >>update.log 2>&1

echo "======================================================"
echo -n "Checking for updates: "
date
echo "======================================================"

docker-compose pull
docker-compose up -d
docker image prune -f

echo ""

Apache reverse proxy:

Code:

# https://helpcenter.onlyoffice.com/server/document/document-server-proxy.aspx

<VirtualHost *:443>
  ServerName my.official.fq.dn

  ProxyRequests Off
  ProxyPreserveHost On
    
  <Proxy *>
    Require all granted
  </Proxy>

  <Location />
    Require all granted
  </Location>

  RequestHeader set X-Forwarded-Proto https
  ProxyPassMatch (.*)(\/websocket)$ "ws://192.168.0.22:80/$1$2"
  ProxyPass / "http://192.168.0.22:80/"
  ProxyPassReverse / "http://192.168.0.22:80/"

  SSLEngine on
  SSLCertificateFile "/usr/local/etc/dehydrated/certs/my.official.fq.dn/cert.pem"
  SSLCertificateChainFile "/usr/local/etc/dehydrated/certs/my.official.fq.dn/chain.pem"
  SSLCertificateKeyFile "/usr/local/etc/dehydrated/certs/my.official.fq.dn/privkey.pem"
</VirtualHost>