SSL certificate to the IP.Chat server

[motomac]

My website is running on HTTPS, and some of my users can't enter the chat because their browsers block insecure content from IPS Chat server (via HTTP). There are only two ways to launch chat on HTTPS:

1. Teach all users every time when they want to enter the chat manually allow loading insecure content 
2. Change chat code to work via HTTPS.

The first variant is impossible for me, so I tried to make second. I had manually edited chat JS-script adding https:// instead of http://. Most of the errors in console disappeared. But I still get one error:

Failed to load resource: net::ERR_INSECURE_RESPONSE

As I see, it's because chat server has self-signed SSL certificate https://server05.ips-chat-service.com/

Is it possible to add correct certificate on your chat servers?

[Rhett]

SSL for chat is not supported at this time, it will be with IPS4 however. 

 

To work around this issue now with a full site as SSL (HTTPS) you can remove the chat link in the nav bar, then add a new link for chat in a pop up using http. 

[Lavo]

SSL for chat is not supported at this time, it will be with IPS4 however. 

​I fail to see how this is a client problem that can be solved with a forum upgrade? Surely this is just applying a SSL certificate to the server, there's a whole bunch of wildcard certs you can pick up and install for cheap.

 

[Rhett]

​I fail to see how this is a client problem that can be solved with a forum upgrade? Surely this is just applying a SSL certificate to the server, there's a whole bunch of wildcard certs you can pick up and install for cheap.

 

​

It's not as simple as installing a cert, if that was all that was needed it would have been done years ago.

As mentioned, ips4 chat will support ssl though. 

 

Thank you

[Joriz]

Looking forward to see IPS4 Chat with SSL.

We also modified our url structure in PublicOutput.php to make the chat work via http:// and many other pages via https://

Please notice if you make your forum work via a secure connection (https://) that visitors in most cases will get mixed content warnings in their browser because many external elements such as added images by the members are hosted at third parties who don't support SSL.

[motomac]

Two days ago IPS team has finally added correct paid SSL certificate to their chat server domains https://server05.ips-chat-service.com/. So I think, IP.Chat now should start working without any browser warnings on HTTPS. Can anybody try? My subscription has expired, and I'm not ready to buy IP.Chat paid plan untill be sure that it will work. Thanks

[Joriz]

This requires changes to the code by IPB. All url's are currently hardcoded as http://

[motomac]

Yes, but you can manually make changes in public/js/ips.chat.js

Find:

iframe.writeAttribute( 'src', 'http://' + serverHost + serverPath + 'web/postMessage.php?parent=' + ourUrl );

Replace with

iframe.writeAttribute( 'src', 'https://' + serverHost + serverPath + 'web/postMessage.php?parent=' + ourUrl );

Find

iframe.writeAttribute( 'src', 'http://' + serverHost + serverPath + 'web/iframeProxy.php?parent=' + ourUrl );

Replace with

iframe.writeAttribute( 'src', 'https://' + serverHost + serverPath + 'web/iframeProxy.php?parent=' + ourUrl );

Find

elem.postMessage( message, 'http://' + serverHost );

Replace with

elem.postMessage( message, 'https://' + serverHost );

Find

elem.location = 'http://' + serverHost + serverPath + '/web/iframeProxy.php?parent=' + ourUrl + '#' + message + '&timestamp=' + Math.round(new Date().getTime() / 1000);

Replace with

elem.location = 'https://' + serverHost + serverPath + '/web/iframeProxy.php?parent=' + ourUrl + '#' + message + '&timestamp=' + Math.round(new Date().getTime() / 1000);

As I remember, it was enough.

[Joriz]

I tried this yesterday. It gave unsecure content error's in Chrome, so I think more changes on the IPS side are needed.

[Lindy]

I tried this yesterday. It gave unsecure content error's in Chrome, so I think more changes on the IPS side are needed.

​If you're using IPS4, can you submit a ticket on this please so we can review? Thank you.

[Joriz]

Nope. Sorry. still running a heavy modified 3.3.x.

We will start do test upgrades to 4.x soon. But it will probably take multiple months before we actually have everything working in production on IPS4

[Lindy]

We're only focusing on SSL'd chat for IPS4 currently. We'll explore IPB soon; I don't imagine it will be difficult, it's just not a priority at the moment.