-
October 1st, 2014, 05:39 PM
#1
SSL problem with self signed certificate
I have a customer running a LS server - exposed on the internet - but with a self-signed certificate. The certificate is not correctly signed for the domain at the moment but it expects WSS connections on port 9696.
If I go here in my browser: https://<hostname>:9696/monitor/
I am prompted by the browser to accept the incorrectly signed certificate and everything works fine.
However, my LS client code refuses to connect on the same hostname and port. I get an endless stream of errors in the Chrome console as it goes through its connect/fail/retry cycle
POST https://<hostname>:9696/lightstreamer/create_session.js net::ERR_INSECURE_RESPONSE lightstreamer.js?v=6.00:204l.pa lightstreamer.js?v=6.00:204e.bk lightstreamer.js?v=6.00:174q.fq lightstreamer.js?v=6.00:251q.Il lightstreamer.js?v=6.00:248q.Hb lightstreamer.js?v=6.00:247m.zd lightstreamer.js?v=6.00:190e lightstreamer.js?v=6.00:51a._callSuperMethod lightstreamer.js?v=6.00:52p.zd lightstreamer.js?v=6.00:256v.executeTask lightstreamer.js?v=6.00:49f
Why does the LS Javascript client behave differently to the monitor in this regard?
-
October 1st, 2014, 05:46 PM
#2
I had to kill the browser and start again - after that it accepted the connection from the LS client
Similar Threads
-
By kpturner in forum General
Replies: 8
Last Post: July 16th, 2014, 09:04 AM
-
By patrickl in forum Client SDKs
Replies: 4
Last Post: December 20th, 2013, 05:06 PM
-
By cwt237 in forum Client SDKs
Replies: 4
Last Post: September 25th, 2013, 10:19 AM
-
By anselme in forum General
Replies: 6
Last Post: February 12th, 2013, 03:46 PM
-
By jonasby1 in forum General
Replies: 2
Last Post: August 4th, 2011, 05:14 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 04:25 AM.
Bookmarks