Browser-sync keeps timing out



I just have a simple html/css/javascript page I’m developing.

I followed this guide;

and here is my code;

gulp.task('serve', ['styles'],  function() {

        port: 8082
    });"dist/*.js").on('change', browserSync.reload);"dev/javascript/custom/**/*.js").on('change', browserSync.reload);"dev/**/*.css", ['styles']).on('change', browserSync.reload);"*.html").on('change', browserSync.reload);


and of course I’m putting the following in my script;

<script id="__bs_script__">//<![CDATA[
    document.write("<script async src='http://HOST:8082/browser-sync/browser-sync-    client.2.12.12.js'><\/script>".replace("HOST", location.hostname));

First thing that happens is the console throws an Mixed Content error. So I change the script tag in the body to https which then causes the connection to browser-sync to time out. I’ve tried changing the URL of the live preview in the browser to http, but chrome automatically reloads it to https.

Hope the issue is clear, let me know if you need any more info,


(Oh I did see there was another support request for this issue when googling, but there wasn’t a conclusive answer to the problem there)

Picture of gulp serve;


still having trouble with this - if anyone has any ideas.


Since the Cloud9 preview pane only supports HTTPS, maybe you can try with HTTP on a separate tab and see if that fares better?



I think this may be progress, however it is now saying the service is unavailable. If you know a fix for that?

Thanks for the help so far!


Hi, I’ve been trying since last week using the same guide and I’m having the same issues. I’ve been taking a look through the BrowserSync API - you can pass

https: true

as an option. This fixes the mixed loading content console log error messages but instead is now throwing me a 503 service unavailable when trying to request the file.



I’ve passed that argument into my gulpfile, but I’m also getting the same error.

I’ll keep you updated to if I can figure something out.


Thanks Alex, same here.

I pulled the same project into localhost and the only change that I made was switching browsersync back to http as a quick test - it launched up straight away so this definitely appears to be a configuration issue to do with https.


Hey C9 guys,

I’m just wondering if there is any update on this or if you can give any pointers on how we might be able to get this working over https with C9.

I have just built a new WordPress starter framework which uses gulp, less, browsersync and a bunch of node modules. It is working great in my local environment but just can’t seem to get around these issues mentioned above in C9.

Is it a port issue, can you open up multiple ports over SSL or is it just not possible due to invalidating security?