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
Proxy config doesn't work with "localhost" it only works with "127.0.0.1" #1979
Comments
Can confirm this issue exists on my machine as well. The docs should be updated if you can no longer use |
I've bumped into this issue. I can confirm not using not using 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 use
proxy: '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.
The text was updated successfully, but these errors were encountered: