You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a docker container with Nginx. It serve a folder src with a simple index.html file.
This container is not directly accessible to the host, it's behind another container with Traefik that act as a reverse proxy.
I can access my index.html via Traefik that relay the request to Nginx with the following address : http://browsersync-nginx.localhost
I setup a Gulp task that launch Browsersync that proxy to http://browsersync-nginx.localhost and in this setup the browser keep loading and loading until it timeout.
When I access the address http://browsersync-nginx.localhost, Chrome take over my DNS configuration and resolve it to 127.0.0.1. So when I proxy it via Browsersync, it resolve with my DNS configuration and guess what.... I forget to declare it in my /etc/hosts 🤣
So after fix my /etc/hosts everything fine.
I didn't know for the .localhost top domain and Chrome. BTW, it's seem that Chrome just follow the best practice : https://tools.ietf.org/html/rfc2606
Hope this report can help other people in the same situation.
Issue details
I have a docker container with Nginx. It serve a folder
src
with a simpleindex.html
file.This container is not directly accessible to the host, it's behind another container with Traefik that act as a reverse proxy.
I can access my
index.html
via Traefik that relay the request to Nginx with the following address :http://browsersync-nginx.localhost
I setup a Gulp task that launch Browsersync that proxy to
http://browsersync-nginx.localhost
and in this setup the browser keep loading and loading until it timeout.Steps to reproduce/test case
I setup a repository with every components required for reproduce the issue : https://github.com/mehdi-ghezal/browsersync-traefik.
The Readme explain how to install every component.
Please specify which version of Browsersync, node and npm you're running
Affected platforms
OS X confirmed, other not tested.
Browsersync use-case
Gulp
The text was updated successfully, but these errors were encountered: