Closed JordanPak closed 6 years ago
Having exactly the same issue. Following Chrome's recent update forcing .dev domains to https, I started using .local domains when developing. Using this type of domain for the proxy causes BrowserSync to timeout when loading any page.
I am having the same issue with domains using .test
by which the the browser is simply not reloading, the gulp tasks loads and watches the files correctly but doesn't reload the page...
[18:13:46] Using gulpfile ~/remote-dev/www/installex/public_html/wp-content/themes/installex/gulpfile.js
[18:13:46] Starting 'sync'...
[18:13:46] Finished 'sync' after 14 ms
[Browsersync] Proxying: http://installex.test
[Browsersync] Access URLs:
--------------------------------------------
Local: http://127.0.0.1.xip.io:3000
External: http://192.168.0.11.xip.io:3000
--------------------------------------------
UI: http://localhost:3001
UI External: http://192.168.0.11.xip.io:3001
--------------------------------------------
[Browsersync] Watching files...
[Browsersync] File event [change] : style.css
[Browsersync] File event [change] : style.css
The same site in a .dev
domain works fine
I'm finding it super super slow since changing from .dev
to .local
, it's not timing out, but to load the page initially it takes about 15 seconds, as opposed to instant without BrowserSync. Once loaded then the hot-reload is quick as you'd expect.
I saw this https://stackoverflow.com/questions/24807786/browsersync-extremely-slow
This was before Chrome basically killed off .dev
, but even back 4 years ago the .local
domain was running slow, but we are all forced to use it now, thanks Chrome.
@CHEWX just use something other than .local
.test
works
@shakyShane As a workaround I'm doing this, but just flagging the issue.
** Sorry for accidentally closing and opening -- hit the wrong button.
I'd like to note that I've tried both .test
and .local
and neither of them are connecting for me.
Hi everyone - I'm closing this issue as it's not directly related to Browsersync - certain OS's have issues with certain domains, and we cannot control/help with that from the Browsersync package :)
hmmm - I now see it working on another .test
domain on my local environment - so for me its inconsistent - will test on a number of domains and see If i can verify a pattern.
Issue details
Hello, Since Chrome now forces
*.dev
to HTTPS, I've had to change my local development URLs to*.test
. However, I'm now having an issue "connection" to a proxy'd site over anything that isn't*.dev
. I've switched to FireFox for testing this.Thank you all for your time!
Steps to reproduce/test case
WORKS:
npm install -g browser-sync
browser-sync start --proxy "wp2.dev"
DOESN'T WORK:
npm install -g browser-sync
browser-sync start --proxy "wp2.test"
The BrowserSync server starts quickly (and takes the same time) in both cases; it's getting the browser to actually connect to the server that's taking forever (and timing out) in the non-.dev case.
Please specify which version of Browsersync, node and npm you're running
Affected platforms
Browsersync use-case
If CLI, please paste the entire command
browser-sync start --proxy "wp2.test"
for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync
gulp: