I use to have it posted that it could take me up to 72 hours to respond to a bug/ticket/post on my site (some times longer, if it is like a few weeks ago when i was ill). I saw the topic over on my site this morning, but early in the week i am typically busy with my regular job, and i try to respond if and when i can and as fast as i can.
Babble requires a Nodejs server of some kind, either being on the same server as the site or on a remote location. I do have a service in the works, but it isn't fully "public" yet. I'll send you a PM to let you know the terms of the service and get the required information i need from you to get you into it, as the CIC will not support babble directly out of the box due to the added requirement of needing nodejs to handle the websocket nature of babble.
when i officially come out with version 3, which will also be the debut of the service version Each person who has purchased the self hosted version of babble (before the release of version 3) will have the option to upgrade to the service version as long as they agree to the terms. after a x amount of time (probably a month or 2) any one who had previously bought the self hosted who wishes to transfer, will need to "subscribe" to the service, which will have its own fee and TOS conditions, and the two will no longer be interchangeable, if you buy the self hosted, you wont have access to the service, you will have to subscribe to the service version and vice versa, you would need to buy the self hosted (similar to how IPS handles IPS, if you are in the cloud and want to go self hosted you need to buy the self hosted and if you want to go into the cloud, you need to subscribe to a cloud package).
https://support.cloudflare.com/hc/en-us/articles/200169156-Which-ports-will-Cloudflare-work-with- you can try one of these ports or contact clouflare for further support. I don't personallyl use cloudflare and know very little about it.
https://codingjungle.com/tracker/babble/init-file-r187/?do=findComment&comment=1403 forgot to roll it over to a tutorial, this is for systemd.
forever is a nodejs app that can be install via NPM, something like "npm -g install forever", forever monitors the nodejs script to make sure it is running and if not, starts it back up. starting node via something like "node babble.js" will only keep that instance of node running as long as the connection is maintained, as soon as the connection is closed on ssh or the terminal is disconnected, it will shut down the node instance. it is why i suggested using forever.
the above mentioned init script is for systemd and the other instructions are for ubuntu (if you using a different distro you will need to adapt for that distro or if it uses another init system, as some might still use sysv or upstart, which i have no plans on writing init scripts for as they are pretty much replaced with systemd in most newer versions of most distro's). the init script is mainly there to keep the process up and running and to start it in the even the server is ever restarted. i can't say the frequency you might do this, my server has only been restarted in a few times over the years, but it is nice to have things start up with it.
But on the product description page you write:
I'm a bit confused about this as I never did this before...
there are two ways to handle SSL in babble. if your site is https, you can not make a connection to a non-secured URL, so you need babble either setup to handle ssl or you can setup a reverse proxy in nginx or a tunneling proxy in apache to redirect babble connection request to a internal non-secure URL. I would highly recommend setting up babble to use SSL over a proxy (as they can be slow, especially the apache one, which also requires some extra configuration. in version 3 i will be dropping support for reverse/tunneling proxies, as the script can now be started in ssl mode and with the service more or less removes the need for them).
configuration of babble is pretty easy, now if you start throwing in the whole ssl/proxy thing, along with cloudflare, you can start to complicate things. I would recommend taking things one at at time:
1. do you run ssl?
no: set it up regularly
yes: decide if you want to invest in configured a proxy for apache or nginx or configure babble to use your ssl certs. again i would configure babble to use the ssl certs.
i've never routed traffic websocket traffic thru cloudflare and i don't know any whoever has. i would contact them for the options that you can do, the linked article suggest creating a sub-domain and routing to that and excluding that subdomain from being "cached" by cloudflare. the other way you can use your server IP address in the "node url" in the ACP, this will however expose your IP, but it is one option available to you. there are also inherit problems with the subdomain method, if you do use a SSL and it doesn't cover the subdomains. I will assist to the best of my ability, but i can't promise to make everything work fine with cloudflare (and imho there are far better solutions out there than cloudflare :))
3. sidegrade to the service
the service isn't "official" yet, but it will soon be and i can add more members to the "trial" that i have going. this removes 99% of the problems you are having with the self hosted. I can PM you the details of the service if you like to see if you want to move to that instead of doing a self hosted.
again to everyone, I am one man if its been more than 2 weeks and i haven't responded to you on my site, send me a friendly reminder