Hi, you need to ensure that the actual URL is a valid HTTPS connection. For example, if you have a non-SSL connection that redirects to a HTTPS one, that is still not valid since the initial connection is non-SSL.

Is this a new feature? I had not noticed either and some of my applications are not behind SSL. Until the last time I checked, it actually worked, but when I saw this question and checked, I discovered that it didn't!

Hi, I have the same issues when I try to connect to my (self signed) server using address https://serveradress:8443/jw. → I'm using Android version 9.0 on Nokia Phone.

iPhone can login using http://serveradress:8080/jw and can't login using https://serveradress:8443/jw.

Actually when you use Mobile Phone/tablet within Android Version greater then 6.0  then I get invalid server or unsupported version. But my old Samsung Tablet which running Android version below 6.0 it works on both https/http. 

People expecting to use the mobile phone in daily business and the mobile version should work:((