-
Notifications
You must be signed in to change notification settings - Fork 34
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
"Write access to end-to-end encrypted folder requires token" out of nowhere (E2EE file deletion impossible with "403 Forbidden") #583
Comments
OK, after resetting keys (including deletion of E2EE files) and uploading E2EE content, everything seemed to work. Unfortunately, now when adding files inside an E2EE folder, the desktop client (Windows or Android, tested both) complains: "upload failed" with no further information There's NOTHING (!!!) in the server logs. I even don't know if this issue has to do something with the initial one. Step by step this freaking E2EE kills itself. What now? |
Tested it over and over again. Now I can provoke / replicate the issue:
No idea what the Android app does here. But it breaks E2EE for the whole server, also affecting the Windows endpoints.
Workaround: step 1 + step 2. NEVER EVER do step 3. So, current E2EE status: |
For me its even easier to replicate the issue. Or it could, in fact, be a completely different one, but as the symptoms are the exact same im appending to your thread. Correct me if im wrong or if I should open a sperate issue. Versions at the time of writing:
I also thought it was a problem of either the Android or iOS app at first because thats where I first saw the issue, but it even happens when the App is not at play, as was the case in my tests. So for me the current E2EE status sadly is: |
How to use GitHub
Steps to reproduce
Expected behaviour
Files are deleted on the server
Actual behaviour
Client complains about "403 Forbidden ..." and server logs errors
Server configuration
Operating system: Raspberry Pi OS
Web server: nginx
Database: MariaDB
PHP version: 8.2
Nextcloud version: 27.1.7.2
Updated from an older Nextcloud/ownCloud or fresh install: Updated
Where did you install Nextcloud from: archive, bare metal
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: local
Are you using encryption: no (only what's needed for E2EE so server-side encryption is likely used)
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: irrelevant
Operating system: irrelevant, multiple clients
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
Seen this before here:
Happens for Windows desktop as well as Android desktop. iOS can not be tested as E2EE is just completely broken there currently (nextcloud/ios#2809, which is a follow-up of nextcloud/desktop#5918 (comment), which is a follow-up of nextcloud/desktop#5564 ...).
I will try to reset E2EE using
/settings/user/security
(once again) now... but this needs to stop. E2EE is so annoying unreliable and breaks on a regular occasion, rendering it the most unreliable part of Nextcloud by far.The text was updated successfully, but these errors were encountered: