Problem Connecting wss:// from Chrome on Android

[SD]

Hi

I am running test application and its working well on Chrome on Windows, Ubuntu, and Android.

I recently made change to enable secure web socket wss:// and its working on Windows and Ubuntu, but on Android it fails to connect with code 1006.

Does anyone else experience this problem?

thanks

[Will Mitchell]

Hi,

I don't think we have seen that issue before. Are you using a self-signed certificate? 1006 is a client-side error code, so I would guess there is something about the connection that Android Chrome doesn't like. Perhaps try navigating to your wss: URL directly using https: and see if there is a certificate error you must add an exception for?

I'm also curious if it is working in Firefox on those platforms. I know Firefox tends to be even stricter than Chrome when it comes to accepting websocket connections.

Android typically auto-updates apps, but it is worth double checking to make sure Chrome is 100% up to date as well. If you have Chrome Beta installed, that could be a good test, too. Let me know if any of that turns up anything.

Cheers,

Will

[SD]

Thanks Will!

I am not using self signed certificate, it was acquired through proper process with a cert authority.   I tried this:

Perhaps try navigating to your wss: URL directly using https: and see if there is a certificate error you must add an exception for?

and indeed there is a cert warning....Once I accepted the warning, the client connected and WORKED PROPERLY.   So I guess there is problem with my cert.  Strange that I do not observe this issue on the laptops and desktops (windows, mac os, ubuntu) but do observe this on Android (tablet and phone).

Thanks for the feedback.... very helpful!

[Will Mitchell]

I'm glad you got it working and happy to be of service. I'm also curious what the error was with the certificate. It is possible that the certificate authority isn't in the Android's list of trusted authorities, but I don't know how to check that.

On a side note, browsers should be slowly moving towards an interface where you are prompted to accept the certificate directly when connecting the websocket. Eventually, that will make it clearer what is going on when things like this happen.

Cheers,

Will

[Warren McDonald]

We have found that valid certs are being rejected as the intermediate certificates are missing from Android, but are ok in Desktop OS. So you might find the root CA for a given authority but not the full chain.

[Warren McDonald]

You can fix this by adding the intermediate certificate at the server side, so that the trust is chain is complete on the android clients. We have had to do this before for certain Certificate Authorities and new releases of Firefox.