Package Details: onlyoffice-documentserver-bin 8.2.2-1

Git Clone URL: https://aur.archlinux.org/onlyoffice-documentserver-bin.git (read-only, click to copy)
Package Base: onlyoffice-documentserver-bin
Description: Online office suite comprising viewers and editors for texts, spreadsheets and presentations
Upstream URL: https://github.com/ONLYOFFICE/DocumentServer
Licenses: AGPL
Conflicts: onlyoffice-documentserver
Submitter: VVL
Maintainer: VVL
Last Packager: VVL
Votes: 4
Popularity: 0.33
First Submitted: 2021-08-11 23:47 (UTC)
Last Updated: 2024-11-29 10:40 (UTC)

Latest Comments

1 2 3 Next › Last »

anarki commented on 2024-11-21 00:17 (UTC)

I can confirm it works fine. Thank you @VVL

SergeantBiggs commented on 2024-11-17 12:47 (UTC)

@VVL Seems to work. Thanks!

VVL commented on 2024-11-17 09:34 (UTC)

@SergeantBiggs thank you. I've added fix to PKGBUILD, you may try it.

SergeantBiggs commented on 2024-11-16 01:01 (UTC) (edited on 2024-11-16 01:02 (UTC) by SergeantBiggs)

@VVL I'm not sure what's the cause of this, but the problem seems to be that the file /usr/share/webapps/onlyoffice/documentserver/web-apps/apps/api/documents/api.js is not created correctly. In older versions (eg. 8.1.3) it seems to contain code, but in the newest versions (8.2) it is 0 bytes. Maybe something needs to be done during the build process to generate this file from api.js.tpl?

VVL commented on 2024-11-13 07:51 (UTC)

I was able to reproduce the problem. I don't see any other way out than to temporarily roll back to version 8.1.3

anarki commented on 2024-11-12 22:53 (UTC)

Have to take that back. After re-creating mariadb and rabbitmq and flushing redis, my admin account is able to use onlyoffice, while others see the error. After logging in once again, admin sees the same error trying to open documents. I'm missing something.

anarki commented on 2024-11-09 21:20 (UTC)

Thanks @VVL. From your list of actions, flushing redis (redis-cli flushall) made the difference for me.

VVL commented on 2024-10-23 12:10 (UTC)

https://help.nextcloud.com/t/nc-29-30-oo-onlyoffice-cannot-be-reached-please-contact-admin/201524/11

VVL commented on 2024-10-22 19:30 (UTC)

I've reproduced your error. Try to make clean install:

systemctl stop onlyoffice-docservice onlyoffice-fileconverter
rm -rf /var/lib/onlyoffice/documentserver/App_Data/cache/files/*
redis-cli -n (YOUR redis DB) flushdb
rabbitmqctl delete_vhost onlyoffice
rabbitmqctl add_vhost onlyoffice
rabbitmqctl set_permissions -p onlyoffice onlyoffice ".*" ".*" ".*"
mariadb -uroot -p << 'EOF'
DROP DATABASE onlyoffice;
CREATE DATABASE onlyoffice;
GRANT ALL PRIVILEGES ON onlyoffice.* TO 'onlyoffice'@'localhost';
FLUSH PRIVILEGES;
EOF
mariadb -uroot -p onlyoffice < /usr/share/webapps/onlyoffice/documentserver/server/schema/mysql/createdb.sql
systemctl restart onlyoffice-docservice onlyoffice-fileconverter
journalctl -eu onlyoffice-docservice -u onlyoffice-fileconverter

anarki commented on 2024-10-22 17:42 (UTC)

After upgrading to nextcloud-30.0.1-1, onlyoffice-documentserver-bin-8.2.0-1 and app onlyoffice-9.5.0, clients can no longer connect. However, administration interface ist able to connect and to configure the documentserver.

Downgrading to onlyoffice-documentserver-bin-8.1.3-1 enables clients to connect again. Can someone reproduce?

1 2 3 Next › Last »