Thanks for clarifying. I’m a little stumped on this one to be honest. It seems like this is almost identical to getting Browsersync and Gulp working on Cloud9 which I’ve done several times recently.
The last two things that look off to me are the
wss:// and the
localhost. External ports are broadcast over
http(s), which I think websockets generally run on if I’m not mistaken, but it could be that actually stating the
wss:// protocol at the beginning of that URL is breaking it.
Also, maybe there’s somewhere in the config that it’s forcing to try localhost rather than your workspace URL. It should broadcast on 0.0.0.0 and then be accessed at your workspace URL (https://workspacename-username.c9users.io:8081). It almost seems like it’s trying to access it on localhost automatically which is breaking it all.
Note: In the Browsersync tutorial, there’s a part where the livereload is configured for your app URL, which may be the key for that working.