Hi Giuseppe,

Yes we are using a self-signed certificate as we are in development mode at the moment, we are a startup and have not moved to prod yet.

I have certainly followed the instructions in the pdf you mentioned.

I've just had a look in the server logs:

11-Apr-14 16:50:51,580|ERROR|ghtstreamerLogger.connections.s sl|LS/SSL AUTH POOLED THREAD 1|Handshake error on Lightstreamer HTTPS Server: General SSLEngine problem on 192.168.1.107:63388.
11-Apr-14 16:50:54,819|ERROR|ghtstreamerLogger.connections.s sl|LS/SSL HANDSHAKE SELECTOR 3|Handshake error on Lightstreamer HTTPS Server: Received fatal alert: bad_certificate on 192.168.1.107:63389.
11-Apr-14 16:50:56,585|ERROR|ghtstreamerLogger.connections.s sl|LS/SSL AUTH POOLED THREAD 5|Handshake error on Lightstreamer HTTPS Server: General SSLEngine problem on 192.168.1.107:63390.
11-Apr-14 16:50:59,820|ERROR|ghtstreamerLogger.connections.s sl|LS/SSL HANDSHAKE SELECTOR 3|Handshake error on Lightstreamer HTTPS Server: Received fatal alert: bad_certificate on 192.168.1.107:63391.
11-Apr-14 16:51:01,577|ERROR|ghtstreamerLogger.connections.s sl|LS/SSL AUTH POOLED THREAD 6|Handshake error on Lightstreamer HTTPS Server: General SSLEngine problem on 192.168.1.107:63392.
11-Apr-14 16:51:04,819|ERROR|ghtstreamerLogger.connections.s sl|LS/SSL HANDSHAKE SELECTOR 3|Handshake error on Lightstreamer HTTPS Server: Received fatal alert: bad_certificate on 192.168.1.107:63393.
11-Apr-14 16:51:06,577|ERROR|ghtstreamerLogger.connections.s sl|S/SSL AUTH POOLED THREAD 10|Handshake error on Lightstreamer HTTPS Server: General SSLEngine problem on 192.168.1.107:63394.
11-Apr-14 16:51:10,819|ERROR|ghtstreamerLogger.connections.s sl|LS/SSL HANDSHAKE SELECTOR 3|Handshake error on Lightstreamer HTTPS Server: Received fatal alert: bad_certificate on 192.168.1.107:63395.

I am not sure why this is happening - as far as I understand the certificate is installed properly.

What the best thing to check next?

Thanks a lot