-
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
Client will not connect unless E2E has previously been set up #560
Comments
how did you build it? Is it Debug or Release? |
My apologies, the issue exists in both Debug and Release @camilasan |
So by random happy accident, I decided to try compiling with clang 6. I looked at my compiler right when the part that is giving the issue was being compiled. It so happens, that there is a build warning in regards to this. (when using clang) (not sure about gcc)
|
OpenSSL Version: 1.10h |
I can't reproduce this error on Linux but I have a similar problem on Windows with Release built. Update: after I updated to Qt 5.11.1 on Windows, I also have the issue with Debug and Release builds... but I still can't reproduce it on Linux. |
I wonder, could having an OpenSSL version of <=1.02 on the server, have any effect on the client? Edit: I Upgraded my OpenSSL on the server and still have the issue, so that's definitely not it. |
Getting the same issue myself. |
Hi! Please try the build https://download.nextcloud.com/desktop/daily/Windows/Nextcloud-2.5.0.61352-daily-20180904.exe. This issues should be solved. Thanks! |
I'm trying to test, but unfortunately because of #279 I can't :( |
@camilasan Do you have commits i can cherry-pick so I can try my own build using old login method? I tried merging master, but I don't think your fixes are in there, as it didn't make a difference. |
No, what changed is how we build it by passing openssl and qt5keychain paths to cmake: |
So yeah, this is still an issue. :( |
@tabp0le Ok, I can't reproduce it anymore. Could you check for client logs? |
I've attached a log using official nextcloud nightly. (windows) |
This is still an issue in https://github.com/nextcloud/desktop/releases/tag/v2.5.0-rc2 (6dae188) |
I had the same issue today, when I installed the new 2.5.0 release (from nextcloud.com) for one of my windows user. After setting up E2E on the iOS client it worked. |
Can confirm this issue still exists in v2.5.0 on Fedora 29. |
Indeed, this should be a high-prio issue and is totally blocking any productive use of e2e crypto yet. I think you know it really needs to be fixed. For alpha stage okay, but at least the client's e2e crypto implementation is said to be stable (v2.5.0 with that feature – and this bug – is released as stable). |
Hey, could there be a problem with the CSR generator in the desktop client? @tabp0le wrote:
From #868:
Code: |
I can confirm that the workaround proposed by @tabp0le works with:
Therefore it must be an desktop client issue... |
Couldn’t get the workaround to work with iOS client. |
The workaround... now the desktop client refuses to sync files. 🙆♂️
|
I'm also geting the Message "GOAWAY received, cannot start a request" |
I am experiencing the same problem. Is there any update on this? I'm really eager to try this out :) |
I have the same problem. Current Archlinux with Client Version 2.5.2git. Build with QT 5.12.2 and OpenSSL 1.1.1b. |
Please, try the daily build from tonight, #1420 is merged and it might fix it :) |
Duplicate of original issue desktop/#830 and fixed by desktop/PR#1420 |
OK, so here's a weird one.
Expected Behavior
Actual Behavior
Logs
https://pastebin.com/N6DfdRsa
Affected Platforms
Linux, Windows, (probably macOS)
OpenSSL Version: 1.10h
QT Version: 5.11.1
Nextcloud Branch: master
To get it to actually work, and add the account, I had to:
The text was updated successfully, but these errors were encountered: