2.7.0-beta3 cannot connect if E2EE-app 1.5.2-beta1 is activated #2223
Comments
|
So from the log, this looks like something fails on the server when uploading the public key... This 409 is kind of surprising, you're sure there's no such key on the server? @georgehrke any idea why the server would reply a 409 after a POST on |
|
Ah! One thing for you @spackmat Could you please try again with debug enabled for the logs? I somehow doubt it'll bring up much more in that case but you never know. |
That route throws a 409 when a public key already exists: @spackmat Can you connect to the server, navigate to Nextcloud's root folder, execute the following command please: |
|
@georgehrke yes, that command fixed the problem! Thanks. I deleted the three folders |
Maybe we want to update the "cleanup procedure" in the 1.5.2-beta1 release notes and the forum post then? I think that step was missing. |
|
And directly to the next problem: I encrypted a test folder, uploaded a pdf file while the app is running and everything works. Then I closed the app, copied a new file to that encrypted folder and removed the other one. Then I started the client again and got a 403 for the DELETE request. While I was writing this message, the client tried again and succeeded. Seems to be still a bit quirky. But the good part is: This is the first time, I got the E2EE to work with the desktop client after years and hours of testing attempts. So hooray and thanks for the progress. |
|
Yes, it should be more resilient to this kind of cases now. If you can reproduce the 403 you mentioned I'm definitely interested in a separate issue with the debug logs (using --logfile and --logdebug for instance) attached. |
Hi, I am testing the new E2EE with Windows client 2.7.0-beta3 and E2EE Server-App 1.5.2-beta1 on NextCloud Release 19.0.1.
I removed the old E2EE-App from the server and cleaned up as stated in https://help.nextcloud.com/t/help-test-the-latest-version-of-e2ee/87590, also removed the whole old windows desktop client and found and removed two nextcloud related entries in the windows login information store (don't know the English name for it, in German it is Anmeldeinformationsverwaltung).
Then I installed and activated the 1.5.2-beta1 of the E2EE app on the server and the 2.7.0-beta3 of the desktop app. This opened my browser and I added allowed the access.
Expected behaviour
I expected the folder to sync.
Actual behaviour
Instead the sync doesn't start. My account is registered inside the desktop app and on the add account screens it also told me the correct count of files on the server for that account. But the icon is grey and on the settings screen it remains in connecting state.
When I deactivate the E2EE app on the server and restart the client, it starts to synchronize and everything works well. When I enable the E2EE app again, the connection cannot be established again. In the logs I can see that a new keypair is created but cannot be uploaded with a 409 response.
Steps to reproduce
Client configuration
Client version: 2.7.0-beta3
Operating system: Windows 10 Pro 1910
OS language: German
Qt version used by client package (Linux only, see also Settings dialog):
Client package (From Nextcloud or distro) (Linux only):
Installation path of client: C:\Program Files\NextCloud
Server configuration
Nextcloud version: 19.0.1
Storage backend (external storage):
Logs
Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.
Web server error log:
Server logfile: nextcloud log (data/nextcloud.log):
The text was updated successfully, but these errors were encountered: