Settings for HTTPS

Node URL = https://www.mysite.com:3000

I tried removing the port ":3000", and removing the "s" from http.

I tried "localhost" instead of my domain.

I've restarted node.js.

None worked.

I've entered:

sslPrivateKey
sslCertificate

The 2 very long strings of text into babble.js. Unless of course I'm entering them wrong. What goes in these?

var sslPrivateKey = ''; //ssl private.key file
var sslCertificate = ''; //ssl certificate.crt file
var sslBundle = ''; //ssl ca.cert file, not always required.

if you are running babble on the same server and don't mind have to use a port, you just set up the SSL in the babble.js.

sslPrivateKey and sslCertificate are required, sslBundle isn't always provided by the cert authority and isn't always used so it is optional. 

in those two required fields, you will need to put the full path to your key file and your cert file (these will be in your apache/nginx configurations) or ask your host for the full paths, they should be able to tell you what they are.

now if you want to run babble without a port in the URL with SSL then you need to configure a proxy in apache or a reverse proxy in nginx. if you do this, you will not need to setup babble.js for ssl. (note: babble.js will still require a port, but it will be used internally)

for the URL you'd use for node URL in the acp,  would be:

https://mysite.com:3000 (if you use a port)

or

https://mysite.com (if you are using a proxy/reverse proxy)

Proxy's in apache are slow and for whatever reason doesn't work with elephant.io, that is what the "alt url" toggle is for, so you can define a http://localhost.com:3000 or the IP of the server. the SSL Tab in general for babble, is for elephant.io incase you need to configure anything additional for the proxy/reverse proxy, I put it in there cause during development we were having issues with the bots, but I have since found a almost 100% way around it and it no longer has issues (so its just there incase it is needed, in version 3 it will be hidden, and will require a constant to be set to show it, to avoid future confusion).

Happy New Year, Michael!

These are the steps I did:

ACP
Port = Yes
Node URL = https://mysite.com:3000
Enable SSL Context Options = ? I left it disabled

babble.js
var sslPrivateKey = /home/site/full_path/
var sslCertificate = /home/site/full_path/

Both full paths include trailing slash.

Regenerated Private Key (also matched in babble.js).

forever stopall and then restarted node.js

I must be doing something wrong.

var sslPrivateKey and sslCertificat still require the single quotes and ; at the end, along with a file name, not just the path.

var sslPrivateKey = '/etc/ssl/certs/mykey.key'; //ssl private.key file
var sslCertificate = '/etc/ssl/certs/mycert.crt'; //ssl certificate.crt file
var sslBundle = ''; //ssl ca.cert file, not always required.

something like that.

YES! I added the file names and Babble is working now!

You are a genius, Michael!

Thank you!

glad its working