-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot edit/open documents (only download) via shared URL after upgrade to 9.1.2 #982
Comments
extactly same problem for me. Same NC version , Same OO version. Updated same on April 12) Read a lot of topic speaking about missing js directory in 9.1.0 but this folder is present in 9.1.2. It seem that no OO server are present. I've updated too my OO server. Not an RP problem, not an acces problem go access to my doc server nicely. Also done deactivated, uninstall and reinstall the OO app in NC. |
xxxxxx@cloud:/var/www/html/nextcloud$ sudo -u www-data php occ onlyoffice:documentserver --check But when in my NC administration panel no server connected |
Solved deactivated, uninstalled, manually download and added to /var/******/app from the git |
@andricas Good to hear. But can u give please some more detailed informations about how u solved the problem? |
This issue is not fully resolved. After backup to previous version and upgrading to news 9.1.2 again, OnlyOffice is no working. |
it also work not by us. Onlyoffice run into docker reinstall or reinstall manualy the plugin not helping us. |
My Solution...
|
For me, I noted that the OnlyOffice |
That adjustment has solved the issue however not sure what it means in terms of security |
opening files via
https://cloud.xxxxx.de/index.php/apps/onlyoffice/126038?filePath=xxxxyyyyzzz.xlsx
works fine.
But shared documents via URLs like
https://cloud.xxxxx.de/index.php/s/EA69mymDsSmt7oX
don't get opened.
The user can only download the file.
With previous version 9.0 all worked fine.
System:
Nextcloud: 28.0.4 (on Debian 12)
OnlyOffice DocumentServer: latest (via Docker, updated on April 10th)
The text was updated successfully, but these errors were encountered: