BrowserSync and Local by flywheel problems

[AKdigital]

npm starts browser sync is trying to access
https://localhost:3000/ and resulting in

localhost unexpectedly closed the connection.

I have
// Project options.
projectURL: 'alonlive.local', - that is my local domain and it works fine when accessing directly.

npm - 6.4.1
CLI version 3.9.1
Local version 3.9.1

Thanks!

If you'd like us to keep producing professional free and open source software (FOSS). Consider paying for an hour of our dev-time. We'll spend two hours on open source for each contribution. Yeah, that's right, you pay for one hour and get both of us (Awais & Maedah) to spend an hour as a thank you.

🚀 $99.99 — Support for one hour or more →
🔰 $49.99 — Support half an hour maintenance →
☕️ $9.99 — Buy us lunch or coffee to keep us trucking #OpenSource →

[KevinHuddy]

Do you have SSL activated on your local project? If my app or website is secure by SSL i have the same result.

[ahmadawais]

SSL is known to cause such issues. Try to disable that?

[eclectic-coding]

@AKdigital Did you get any resolution? For what is worth, I was having the same issue with Valet. But when I included the protocol in the config, it now works just fine:

projectURL: 'https://sandboxwp.test',

[isvictorious]

@AKdigital This is a known issue with the .local domains on OSX. For all new sites, I recommend using .test or local.yoursite.com.

Issue with .local is it has some loop back that causes connection issues.

[ashbryant]

I'm having issues with this also and would like to know how to fix it.

[benjaminadk]

The BrowserSync is confusing. I'm using XAMPP at localhost/wp_vs_532 and put that in the config file. But hot reloads weren't working. I noticed the message about port 3000 and tried localhost:3000/wp_vs_532 and now it works. I know Apache is on ports 80 and 443 so it seems like wpgulp takes the input url and spits out updates over port 3000 of that url???

[mykt0ngc0]

Updating Local to the latest version might help.
https://localwp.com/releases/