-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
SSL initialisation failed #1960
Comments
Found details about regression in Android 7.0: https://issuetracker.google.com/issues/37122132 |
I reissued the certificate with prime256v1 curve and got it working. |
Hello.. can you please let me know if you're aware of any regressions? Samsung S8+ with same behaviour, with latest version of NC app. |
Actual behaviour
The app is unable to establish initial connection with the host. This error is shown:
"SSL initialisation failed"
Expected behaviour
The connection should be established and user should receive a possibility to log in.
Steps to reproduce
Environment data
Android version: 7.0
Device model: Samsung J530FXXU1AQI3
Stock or customized system: stock (Samsung Experience - 8.1)
Nextcloud app version: 2.0.0 (tried both Playmarket and F-Droid)
Nextcloud server version: 12.0.4
Logs
Web server error log
No logs
Nextcloud log (data/nextcloud.log)
No logs
The thing is that the issue is more than weird. I do have an older smartphone Meizu M2 with Android 5.1 and Flyme OS 4.5.3I and Nextcloud app is working well with Nextcloud server.
Here is server SSL configuration:
The certificate is generated with secp384r1 elliptic curve and Must-Staple extension, however that shouldn't be a problem, since it is working with older Android.
I commented each additional directive one by one until just a standard SSL setup left and tested the app but it didn't connect.
Unfortunately, the device is not rooted and I'm not able to get logs from Samsung, tried with CatLog.
Server details if needed:
OS: Ubuntu 16.04
Web server: Nginx 1.13.6
OpenSSL: 1.1.0f 25 May 2017
PHP: 7.0.15
The text was updated successfully, but these errors were encountered: