LiteSpeed support

Node is server agnostic, the only thing in babble that would be server specific is if you need to setup a reverse proxy. 

The new version of babble, 2.2+, will warn at different stages of node disconnection. if you go to babble, and it show the disconnect message immediately, then node script is not running (or the url/port is incorrect, or if you have reverse proxies setup, then they have failed). if that is not the case, and you send the first message, and then it tells you its not connected, then i'm 99% sure, its a private key issue, that is not the same in the babble.js file and in your acp.

Thank you Michael. I will install the latest Babble version. I gave up on it for awhile, but will try again.

root@host [~]# forever start /home/site/public_html/forums/applications/babble/sources/Node/babble.js
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info: Forever processing file: /home/site/public_html/forums/applications/babble/sources/Node/babble.js

root@host [~]# forever list
info: Forever processes running
data: uid command script forever pid id logfile uptime
data: [0] 1b-w /usr/bin/node /home/site/public_html/forums/applications/babble/sources/Node/babble.js 5136 5138 /root/.forever/1b-w.log 0:0:0:20.844

I got to babble on the site, and it doesn't show "Babble is not connected to the node server, please contact the administrator!" for a few seconds, but then it shows up.

I check netstat for port, 3000 is open and listening:
root@host [~]# netstat -an
Proto Recv-Q Send-Q Local Address Foreign Address State
.
.
tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN

My name eventually shows up in the online list, but I still can't enter anything into the chat. Still showing "Babble is not connected to the node server, please contact the administrator!"
I refresh the page, no one in the online list, I enter a message and "Babble is not connected to the node server, please contact the administrator!" comes up.
Trying from multiple networks, without firewall.

you do have the node url set?

Yes. Url is set to my site at port 3000.
And I have reset the private key, checked the .js file to verify, and then reset the node by forever stopall, and rerunning for forever ./././babble.js

could i get access to your site? you can send me the info in a PM.

Thanks for the help!

for the record: turned out to be cloudflare. Putting the IP address in directly to Node URL seems to have fixed the issue. Since we use cloudflare mainly for Caching (not security), this isn't an issue.