-
Notifications
You must be signed in to change notification settings - Fork 801
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
[Bug]: Useless error notifications while sync is stuck: server responded with an error while reading directory #5356
Comments
Same issue reported by this user: https://help.nextcloud.com/t/server-responded-with-error-when-reading-directory-operation-aborted/139572/2 |
This seems to be a server bug. Server also cashed: The server encountered an internal error and was unable to complete your request. |
Also seeing the same problem, |
@szaimen could be but i reinstalled the desktop client 3 versions back from the mentioned above and keeps spitting the same errors. Windows clients seem unaffected. Unfortunately nextcloud's logging is very poor and I cannot seem to find any explanation |
But also if the desktop app manages to crash the entire server because of this, this may be a good way to exploit the server. I see a denial of service here. |
For security issues see https://hackerone.com/nextcloud |
I do not have a POC, just may be a good start for a test @szaimen. I see not point in reporting this here. After some further digging I am pretty confident that the above errors are caused by a hardcoded chunk size in the desktop client. The chunks used are rather large and do not seem to being adjusted automatically, which I would recommend as fix. Network limitations should be taken into account when using this. When I manually overwrite the chunksize of your app it runs without problems. |
okay, then it looks like the issue is located correctly in the desktop repo. |
Hi, any update on this ? |
i am unsubscribing from this thread as I stopped nextcloud because of continuous issues like this one. |
Been getting a lot of "Operation cancelled: directory not found" while syncing from one computer to another. I saw a GH issue back from 2021, closed due to inactivity. Nobody seem to care for the usability of Nextcloud :/ |
Same issue today with NC30! aggh! |
I had to disconnect the client, remove the directory on the local machine and add the account again for it to sync properly. |
I created a new issue for the latest 3.14.0 desktop client release. See pr referenced above. It's giving the same very vague error messages. But clearly it's not a server issue, they should change the error messages. I also created a new issue, because is could this time pin point the exact version of where it went wrong and which versions still worked. Since this ticket is about client version 3.6.6. |
Bug description
Nextcloud creates very unhelpful errors.
This list continues for ever since the latest update of the desktop client. No option to find any reason for it. When looking in the settings window it shows some on a metadata folder that has not been modified since 2015: operation cancelled.
Removing this folder had no effect on the stream of errors nextcloud is creating.
Steps to reproduce
Expected behavior
A normal working product without data loss and constant sync errors.
Which files are affected by this bug
unclear
Operating system
Mac OS
Which version of the operating system you are running.
13.0 (22A380)
Package
Appimage
Nextcloud Server version
25.0.2
Nextcloud Desktop Client version
3.6.6
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
No response
The text was updated successfully, but these errors were encountered: