Issue Summary Browsersync used to work with HTTPS, but stoped working a few weeks ago. So, for instance, I had a localwp site at https://playground.mydomain.test , and was able to run: browser-sync start --proxy https://playground.mydomain.test and access the site at https://localhost:3000 (after …

btw I realized I can just not enter my password at the prompt to update the hosts file, and my changes will stick with the warning “could not update hosts file.” So, only every once in a while when I add a brand new site to Local will I have to enter my password to have it add new records (which wil…

Browsersync for HTTPS

Support

aquamarine August 2, 2023, 5:17pm 15

Sounds good, thanks for your help!

Feature request opened.

1 Like

Topic		Replies	Views
Browsersync HTTPS Compatibility Feature requests	0	334	August 2, 2023
Browsersync will not load localhost:3000 Archived Support	8	2931	March 12, 2023
BroswerSync Proxy fail - Site Not Found Support windows	2	94	May 29, 2024
Using Browser Sync WordPress Questions	3	2288	May 11, 2023
Browsersync and Gulp not working Workflow hosts-file , windows	2	7428	December 20, 2018

Browsersync for HTTPS

Related topics