Browsersync for HTTPS

I’ve checked with the team but there isn’t any workaround we have handy to provide that would get around what you’re running into. It’s really just a limitation of using Local in this way that is a bit unavoidable. I did some searching and saw that someone created a Feature Request related to this some years back, but it never got any traction.

If you wanted you could create a new Feature Request for others to vote, comment, and follow for updates. We often check these for future enhancements to the app.