# Browsersync for HTTPS **URL:** \ **Category:** Support\ **Created:** [July 7, 2023, 2:03pm UTC](https://community.localwp.com/t/browsersync-for-https/37960 "2023-07-07T14:03:25Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\ **Post date:** [July 13, 2023, 5:51pm UTC](https://community.localwp.com/t/browsersync-for-https/37960/3 "2023-07-13T17:51:48Z")
Hi @aquamarine Thank you for all of your detail here. I think we’ve seen similar issues with Browsersync in the past, but as far as I know, there isn’t an exact fix. As Ben noted below on a similar thread, it can be finicky at best. > [@Browsersync will not load localhost:3000](https://community.localwp.com/t/browsersync-will-not-load-localhost-3000/35617/6): > > Hey @irenehardy – Thanks for those extra details. It’s hard to know for sure what’s going on without seeing actual errors within the Browser console, but one thing I notice is that the gulpfile.js config is using https as opposed to regular http. My guess is that Browsersync is having issues connecting over HTTPS to the Local site. I know that it’s possible to get Browsersync to work with an HTTPS backend, but I’ve always felt that it’s been finicky and more trouble than it’s worth. As a start… --- _[View the full topic](https://community.localwp.com/t/browsersync-for-https/37960)._