New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BrowserSync does not work with a proxy on docker host. #1971
Comments
I found JS error in chrome console for https://domain.test:3000/:
|
Never mind, in my case it was the same as in #1968, though I had the same I was able to solve it by removing the async option from the snippet:
|
Could you solve your issue @asannikov ? |
Hello, this is still an issue for me as in Magento we cannot (in fact we can, but it needs some tricks) load the script before require. |
@felixranesberger @MeCapron |
Issue details
BS is installed on docker host. But i tried to use it on local host as well. The result is the same.
All ports are accessible:
https://domain.test:3000/ => shows website
http://domain.test:3001/ => shows BS dashboard
CLI shows:
on any change in the files of the website, BS catches changes but does not refresh the browser.
`[Browsersync] Reloading Browsers...``
I tried different browsers: Chrome, Safari, FF.
Steps to reproduce/test case
Used docker environment: https://github.com/markshust/docker-magento.
after install:
configure ports in
docker-compose.yml
:Then call from the project root on your local host:
bin/root npm install -g npm@8.12.1
bin/root npm install -g browser-sync
bin/bash
and there create a config file, provided belowCall it form the container (on bin/bash):
browser-sync start --config bs-config.js --no-open --https`Please specify which version of Browsersync, node and npm you're running
Affected platforms
Browsersync use-case
If CLI, please paste the entire command below
browser-sync start --config bs-config.js --no-open --https
for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync
bs-config.js file:
The text was updated successfully, but these errors were encountered: