Improve error handling for connecting to server

[JamesonFinney]

I've noticed that when connecting the client to a server, at least two scenarios result in the same error message:

• Attempting to connect to an HTTPS sever with an invalid or self signed certificate
• Connecting to a new version of the server with an older client

Ideally these situations would be handled in such a way as to result in different and descriptive error messages.

System: Mac OS X El Capitan

[richardwlu]

Our users are having the same issue with the latest version on Windows.

When the user attempts to connect to our https instance, it fails to connect as a valid instance and attempts to fall back to http in the input box.

Is there a solution for this?

[rodrigok]

Are your instances running with a valid SSL or self signed?

We do not support self signed certificates, if you are using one you should generate a CA certificate and install each machine.

[richardwlu]

We're using self signed. We have generated CA certificates and installed on all machines. It was working previously but for some reason when they updated to the latest version of the desktop client it fails to connect. I'll take a look at the certs on the desktops again. Any other thoughts are appreciated!

[rodrigok]

@richardwlu we didn't change anything related with that, but can be a problem with Electron since we upgraded to the latest version.

[rodrigok]

Fixed by 0b86ae9