-
Notifications
You must be signed in to change notification settings - Fork 793
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
Uploding e2e encrypted files seems to take forever/fails #890
Comments
Any news here what I can do to troubleshoot/debug this, or is this "expected"?? |
Testing with a new user and although the setup works and it partially even syncs, it also seems to fail at some point: nextcloud/android#3291 (comment) |
+1, same issue here. |
+1, files put in an encrypted folder do not upload, blocking client forever. happens on iOS and macOS client. e2e not useable at all. |
Did I also already mention it actually blocks any file upload, even if you have multiple users connected in your desktop client and only one has this issue? |
I have the same problem here, with the linux 2.5.1 AppImage and on windows. |
Same issue with 2.5.1 on windows. When i set a directory as encrypted on windows, the upload of files in this directory does not work on Android. |
Same issue here on macOS (v2.5.2). Is there any known workaround? |
IMHO it is quite troubling that no one from Nextcloud commented on this issue… Is this expected or what? What can we do? etc.… E2e crypto is really not well-developed in Nextcloud. I don't like to say that, but in the current state is just absolutely unusable. |
@rugk same feelings here. I'm currently testing Nextcloud with the goal to eventually completely switch from other Cloud providers and the E2E feature seemed like a huge selling point. Unfortunately it simply does not work. I understand new things need time to mature and it's quite early days for E2E within Nextcloud. But at least some sort of workaround or at least feedback would be .... nice. |
Had e2ee never get to work due to this problem on different NextCloud instances on different servers and users with different computers. Everywhere the same: when the desktop client tries to add a file to an encrypted folder, the folder breaks. Meaning that also the android client cannot upload new files after that. Today, I tested v2.6.1-rc1 very hopeful, but still doesn't work. And no feedback. And e2ee is on the market since several major versions of NextCloud, so I would expect it to at least work at all. |
I suspect that no one really uses the E2E encryption feature because it is still in the alpha stage (since a long time). Sadly it seems that because of that the developers think there is no demand for E2EE and virtually stopped working on it. Or maybe there really is too little demand. |
@0x47 regarding the amount of issues targeted against E2E and given the activity there (at least initially) there is quite a high demand. But: "Nextcloud + E2E" is waaaaaaaaay better than "Nextcloud" - but it does also works the way it ever has, so I can wait till ready. Nevertheless, its sad to see there is no official communication/activity/whatsoever around this feature. |
I also think that the demand is high. There are companies like Boxcryptor who sell software for encrypting files stored in cloud storages. But i'd like to see this feature implemented in NC natively. But as @0x47 said: the current E2E-feature is completly unusable. |
@marbetschar I am not sure what you mean by
but for me the E2EE has never worked for the desktop client. So from my point of view the developers are too busy/lazy to essentially copy/paste the somewhat working Android E2E code to this desktop client. Anyway, I have so many other issues with this desktop client that I have to use the OwnCloud client most of the time (crashing when using HTTP2, broken sync when using umlauts in file names, crashing due to unknown reasons) - sorry for the off-topic. |
@0x47 I meant the fact, that Nextcloud always worked without E2EE. And it continous to do so. That said, there is no urgency of getting it done. Neither for Nextcloud developers nor for Nextcloud users - especially if Nextcloud developers get paid for other features. I don't want to say I'm supporting this prioritization, but I'm not a Nextcloud developer. Overall its disappointing how the whole E2EE stuff went so far - at least communication wise. UPDATE: I did not experience any desktop sync client issues so far without using E2EE - so I can't say anything about potential issues there. |
Thank for the clarification, it is a valid point. For me personally, coming from Seafile with working encryption (granted, not with the best concept), the features is a must-have mid- to long-term. For me, it is the single only feature that makes it better than Seafile. I guess I was too excited about this and switched too early. |
IMHO that's exactly the problem. Happened to me as well. Nextcloud said the feature is ready - and as problems occured, Nextcloud went completely silent. One might argue they still provide the impression of readiness, calling it an "Enterprise-grade Encryption Solution": https://nextcloud.com/endtoend/ The sad truth is E2EE is far from ready - and calling this feature an "Enterprise-grade Encryption Solution" is .... well, its too far of a stretch. E2EE, at this stage, should have never been released to the public in the first place. |
If you only use the Android app E2EE works fine. It's the desktop client that's broken. They created a new RFC that should fix the whole encryption process but it's not yet implemented. Also, E2EE is not compatible with Nextcloud 17. So, yeah, E2EE in it's current state, is more or less broken. I really hope that gets fixed soon. OT:
Are you using MySQL as database? My server uses HTTP2, I've got many Umlauts and special characters in my files (stored in german, french, russian and greek), and the client never crashes here. I've only heard MySQL might be the problem in this case (I'm using PostgreSQL, but MariaDB should work too). |
That sounds interesting, do you have a link? |
More or less, I had a few links pointing to all open issues but I can't find them now. That's the only one I could find: nextcloud/end_to_end_encryption_rfc#34 Unfortunately, the issue doesn't include any details. I know I've created a issue on GitHub talking about it, but it got closed. The end results was that a new version of the RFC has to be implemented and all files/folders have to be re-encrypted. Edit: My original issue: nextcloud/end_to_end_encryption#94 |
Let's not take the OT too far, as it is another big issue beyond the scope of this thread. I use MariaDB and the issues are described here:
Fact is: none of the issues are happening with the OwnClient client - so I doubt the DB is the reason. |
I can't seem to reproduce the initially reported behavior with current master. I'll take the liberty to close this one, but please reopen it or open a new one if that shows up again with upcoming 2.7 releases. |
I'm experiencing the same issue on Fedora 32 AppImage version 3.0.2. Nextcloud server version 20.0.1 (also same with 20.0.0) - using docker. The issue recreates reliably for me, and it did so many times. Create an empty encrypted (e2ee) dir, then add like 50 or more files to it. Syncing gets stuck. If I do the same without e2ee folders, it works okay. E2ee is not production ready if a client app cannot sync e2ee. It's far beyond usable if I cannot do this basic thing. |
Same here with NC 20.0.1 and client 3.0.2 on Manjaro. When I create encrypted folder with 10 files, maybe 3 are uploaded and then whole process gets stuck and doesn't move for hours. When I cancel sync, 3 uploaded files appear on cloud and are synced to other clients. When I restart sync, few other files are uploaded and process freezes again. So I agree, this is not usable in production. 😞 |
05/12/2021 and this don't work at all on desktop error 503 when upload and 404 when download E2E is a "BUG" not a "FEATURE" |
Perhaps this ticket should be reopened (unless there are new tickets created about the same issue), since other people are still experiencing uploading problems with e2ee. I've stopped using e2ee because my situation is different now (I have my own HW infrastructure and currently I'm the only user), but in any other situations I would be very keen to have e2ee working. |
I have less than 500kB files to sync (in two files) for testing. However, as far as I see they never really uploaded.
Likely also related to the issues on the Android side: nextcloud/android#3291
Expected behaviour
Sync.
Actual behaviour
It seems to retry syncing these little files and always seems to fail:
Currently:
In Nautilus I do see by their icons that it only tries to sync the (to-be) e2e encrypted folder.
Before (a try some days ago) also like this:
(Note the progress bar is not moving here – it can stay like this for minutes…)
Note it often does not even count the files (two files) correctly.
Steps to reproduce
Client configuration
Client version: 2.5.0git 371001c
Operating system: Fedora 29
OS language: de_DE
Qt version used by client package (Linux only, see also Settings dialog): Qt 5.11.1, OpenSSL 1.1.1 FIPS 11 Sep 2018
Client package (From Nextcloud or distro) (Linux only): distro
Installation path of client:
/usr/bin/nextcloud
Server configuration
Operating system: Debian-based
Web server: nginx
Database: mysql
PHP version: 7
Nextcloud version: 14
Storage backend (external storage): no
Logs
(put into details tags)
nextcloud --logwindow
ornextcloud --logfile log.txt
(On Windows using
cmd.exe
, you might need to firstcd
into the Nextcloud directory)(See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files)
Web server error log:
grepping for
end_to_end_encryption
found nothingServer logfile: nextcloud log (data/nextcloud.log):
Searching in the web UI logs (for "encryption"), I get many of these:
…many of these:
…and nothing special anymore:
The text was updated successfully, but these errors were encountered: