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
🐛 BUG: default 0.0.0.0
wrangler dev address not routable in Windows
#1652
🐛 BUG: default 0.0.0.0
wrangler dev address not routable in Windows
#1652
Comments
Can confirm it's not routable in Windows, a simple fix could be using |
Another solution here might be to print all of the available network adapters, like
Or
Windows probably isn't the only place that |
@Skye-31 Since you are picking this up here is a reference to the recent PR that caused this issue in Windows, we need to be able to support the VM/Container environments as well which prefer the reference: #1605 Cc: @WalshyDev since you were on that PR too 😄 |
My plan is to list all available addresses, so this should cover that 🙂 |
@JacobMGEvans I filed the original issue you mentioned, and just wanted to give my two cents and to confirm what @Skye-31 said, that keeping the |
Created 2 PRs. One solves the |
Re-opening this as the issue of what is displayed to the user is only fixed in local mode (i.e. in Miniflare) and not in remote mode (i.e. when using the proxy.ts code). |
@petebacondarwin, have also made a PR at #1881 to resolve this 🙂 |
What version of
Wrangler
are you using?2.0.25
What operating system are you using?
Windows 10
Describe the Bug
When using
wrangler dev
orwrangler pages dev
, you'll get output like this:Previously, you could click on this and open up your browser without issue, as well as of course
b
opens this address too.Unfortunately, at least within Windows,
0.0.0.0
isn't actually a routable address, and the browser throws aERR_ADDRESS_INVALID
error, and something like this:It seems like this address may be routable in some OSes, but not Windows. This seems to be due to the changes in #1605
The text was updated successfully, but these errors were encountered: