Open NathanBowers opened 2 years ago
Can confirm this issue exists on my machine as well. The docs should be updated if you can no longer use localhost
and instead must use 127.0.0.1
instead.
I've bumped into this issue. I can confirm not using not using localhost
but instead using 127.0.0.1
also worked for me.
Is this a browsersync issue? I thought it might be something related to a new router I've added with DNS rebind protection enabled or perhaps an update to MacOS?
This is still an issue.
Issue details
Documentation says that
proxy: 'localhost:4567'
will work. In the past it did work but as of now localhost doesn't work and I have to useproxy: '120.0.0.1:4567'
instead. I'm using Ruby Middleman static site generator with gulp to build static assets and startup BrowserSync.If I gulp config
proxy: 'localhost:4567'
the BrowserSync UI server starts ok but trying to browse tolocalhost:7000
hangs as if no server is started there. I can browse the Middleman server atlocalhost:4567
fine, it's just not being proxied.I don't mind using an IP address instead of localhost, but the documentation all says that localhost works and this was a breaking change after I recently upgraded all my node packages, gems, ruby, and macOS.
Steps to reproduce/test case
My simplified gulp file init:
The full codebase is at https://github.com/NathanBowers/mm-template if that helps.
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
{cli command here}
for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync
Here's the init from my gulp file:
The full codebase is at https://github.com/NathanBowers/mm-template if that helps.