Document cannot be saved, please check your permissions when ugraded from 25 to 26.0.7 - 27.1.6 #3255
Assignees
Labels
Comments
|
Does the problem go away if you disable the |
|
Nope, I just tested with the maps app disabled and it still does the same thing. I also tried upgrading to v8.0.6 of the Richdocuments app [Nextcloud Office] and it didn't fix it either. It is definitely a lock time issue like the logs show of some sort, because the new odt file also can't be deleted immediately, but after the dialog pops up twice [at least on my machine] then the document is savable and tends to be deletable. |
|
Do you have the files_lock app enabled? Otherwise can you share the log error for the delete as well as the output of |
I assume you are asking about the app called "Temporary Files Lock" which appears to have that internal name then no, we have never had it even installed. Logs#OCC Config:list Error
Console Log
Delete Logs |
|
+1 for the same issue on my two instances. |
|
We've got the same issue on one of our instances:
The We do not have the temporary-files-lock app enabled. |
|
Same here
A newly created document can also not be deleted for a while until I tried to save a few times and the lock is apparently released. Nextcloud occ config:list Logs: I might add, that I have another nextcloud instance that is connected to the same collabora instance, that does not have this problem. Disabling file locking in the Nextcloud config "fixes" the problem. |
|
We have the same issue with a Nextcloud 26.0.4 running Collabora. When the "no permissions" warning happens, the affected files also cannot be moved, deleted or even renamed in Nextcloud, so this does not seem to be a Collabora-specific issue (only). Disabling the Temporary File Lock app did not solve this for us (and as we used managed hosting we have no access to config or occ). |
|
Any updates on this? |
NathanaelA
changed the title
|
I've upgraded today to the latest 27 and all dependencies --
Just an additional data point I was using the latest Redis 7.0.x, I also upgraded [& purged all data] to 7.2.4 and tried both the normal image and the Alpine version, no differences. the issue is still present. |
|
The problem is suddenly gone in two of my Nextcloud instances after updating to:
Which one of those two Version upgrades leads to success is not clear. There are nothing in the changelogs what explains this? |
I can confirm this. |
|
For us the upgrade of Nextcloud and Collabora did not solve the issue, but disabling the preview-generation did. |
|
same here, its previewgenerator i think. at least the combination of previewgenerator + collabora EDIT: No i was wrong, disabled the previewgenerator and still no success |
|
We figured that this happens at times when Nextcloud tries to access the Collabora instance via a private IP. Does setting |
mejo-
added a commit
that referenced
this issue
Jul 24, 2024
Makes sure we always set a sane timeout and `allow_local_address`. Fixes: #3255 Fixes: #3435 Fixes: nextcloud/server#44190 Signed-off-by: Jonas <[email protected]>
3 tasks
mejo-
added a commit
that referenced
this issue
Jul 24, 2024
Makes sure we always set a sane timeout and `allow_local_address`. Fixes: #3255 Fixes: #3435 Fixes: nextcloud/server#44190 Signed-off-by: Jonas <[email protected]>
backportbot bot
pushed a commit
that referenced
this issue
Jul 25, 2024
Makes sure we always set a sane timeout and `allow_local_address`. Fixes: #3255 Fixes: #3435 Fixes: nextcloud/server#44190 Signed-off-by: Jonas <[email protected]>
mejo-
added a commit
that referenced
this issue
Sep 6, 2024
Makes sure we always set a sane timeout and `allow_local_address`. Fixes: #3255 Fixes: #3435 Fixes: nextcloud/server#44190 Signed-off-by: Jonas <[email protected]>
|
Has this been fixed? |
|
@roelofz this should have been fixed with richdocuments app version 8.4.4. Please check if you're running a newer richdocuments app version than 8.4.3. |
|
Maybe a blond question but where can I find the rich documents app in apps? |
It's called "Nextcloud Office". The internal name is "richdocuments". I see that this can be confusing 😉 |
|
Thanks for the clarification! |
|
This is really puzzling me, it seems only to appear when editing xlsx sheets, docx seem to work. |
|
I am getting this issue as well. I recently installed NC for the first time and I am using the AIO. Collabora logs show 403 forbiddena and this is on all files. I am on 8.4.6 as well. I am able to upload to my main directory just fine and opening any file is fine, just seems editing is the issue. I can provide logs where needed. |
hcvcastro
pushed a commit
to hcvcastro/nextcloud-richdocuments
that referenced
this issue
Nov 21, 2024
Makes sure we always set a sane timeout and `allow_local_address`. Fixes: nextcloud#3255 Fixes: nextcloud#3435 Fixes: nextcloud/server#44190 Signed-off-by: Jonas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Document creating worked before upgrading NextCloud and Collabora.
Creating new documents that use the richdocuments interface cause the following error to appear:
Document cannot be saved, please check your permissionsat the start of the document editing session and for the first minute or so until whatever background task unlocks the file.To Reproduce
Also have seen where opening this same document later it might have the same issue. It does Save the document eventually, but throws this error up frequently until the it works. Once the lock clears [I assume based on the logs] everything seems to be good.
Expected behavior
The document to save without any errors.
Screenshots
Client details:
[We tested from a wide range of devices, seems to be a purely a server side issue]
Server details
Operating system:
Ubuntu - running the Community Docker Nextcloud 26.0.7 & 27.1.6
Web server:
Apache reverse proxy
Database:
MySQL 8.0.31 / 8.3.0
PHP version:
PHP 8.2.11 / 8.2.15
Nextcloud version:
26.0.7 / 27.1.6
Version of the richdocuments app
8.0.5, 8.0.6 / 8.2.4
Version of Collabora Online
23.05.5.2.1 / 23.05.8.4.1
Logs
Nextcloud log (data/nextcloud.log)
This is a fairly busy server but these were ALL the logs for this file "testing888.odt" that I created. I used grep to filter them out, however manually looking thru the logs I didn't see anything else related to it on either side....
Browser Console log
Browser Network
No other errors the rest of the network panel was all successes.
Server Collabora Logs
The text was updated successfully, but these errors were encountered: