Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Error when connecting to server with self-signed SSL. #705
When connecting to a server that has a self-signed SSL certificate, the client errors out before allowing you to login to the server due to a certificate error.
Because I checked "Trust this certificate anyway", client should proceed with the certificate trusted and be able to function normally.
I get a Chrome-looking error screen that says ERR_INSECURE_RESPONSE.
For the record, I can access the server through Chrome once trusting the certificate, the issue isn't server side.
Steps to reproduce
Client version: 2.5.0beta1 (build 20180803)
Server configuration is not relevant to the issue, it works without HTTPS and also works with a valid SSL certificate, issue seems to be isolated to self-signed SSL certificates.
I have a reverse proxy for external access that terminates with a valid Let's Encrypt SSL, but within my server's private LAN I use a self-signed SSL to simplify management, which is where this particular client is. I can mitigate this problem for now by either using HTTP (which is fine since it's local anyway) or by routing the connections through my SSL termination proxy that corrects the certificate, however this worked fine in previous versions of the client with the self-signed certificate.
I guess this SSL certificate is expired, which may be why, but I do have older Nextcloud clients that are working fine with this certificate. I would think that once you check that "trust this certificate anyway" checkbox, all validation other than "is this the same certificate?" should not be considered. My SSL termination proxy doesn't care that this backend certificate expired, nor do my older Nextcloud clients on this LAN that are still syncing with this server.
I have a similar issue, my server certificate has expired, when I click on "trust anyway" I either get a chrome like error.
I will be very happy to have a look at it.
If anyone already has a fix please feel free to push it.
If you're on a Mac then downgrade to 2.33 and install that version, it should install (it did for me). Make sure you delete the current version first. Once you've set up the older version (your login details) you can reinstall 2.5.*. But first of all you need to move the files in 'Library/Application Support/Nextcloud' to 'Library/Preferences/Nextcloud'.
It should work fine on installation. I should add that I did this on a new installation. I don't know if it may or may not cause problems down the track.