How to make Microsoft Edge work with VVV sites #1523
Comments
|
What's the error message it gives under details? As an aside, the src
subsisting is going away due to changes in core development, you should use
build instead
…On Thu, 24 May 2018 at 18:23, Andrea Fercia ***@***.***> wrote:
Microsoft Edge has network problems, especially for unusual network stuff.
It's impossible to see a VVV site in Edge. It's a known issue, just google
for "Edge Hmmm... cannot reach this page" and you will find tons of reports
and suggestions. 99% of them didn't work for me.
[image: screenshot 3]
<https://user-images.githubusercontent.com/1682452/40501201-7c383c7a-5f87-11e8-979d-00e0cf44e9df.png>
It's an Edge bug, nothing wrong with Virtualbox and VVV.
Eventually, I've found a solution but it requires to edit a Windows
registry key, For people who need to test with all browsers, worth
considering to document the fix. See this comment:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10142843/#comment-8
You can workaround this issue by changing your VirtualBox Host-Only
Ethernet Adapter’s "*NdisDeviceType" to 0 and rebooting. You can find the
key in
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e972-e325-11ce-bfc1-08002be10318}\00XX.
The downside to this is that now you’ll have an “Unidentified Network” in
your Network and Sharing Center. It’s also managed by Windows Firewall now
and by default it is in the Public Profile and it can’t be really changed
easily.
For me, the path to the registry key was slightly different and ended with
\0016, I guess the commenter meant to search in any of the sub-folders
that start with 00. The key to edit is *NdisDeviceType (it really starts
with an asterisk) and needs to be changed from 1 to 0.
Being a registry edit, people should really know what they're doing, so in
any case a registry backup, or bookmarking the key to easily find it again
and revert would be highly recommended.
What I'd suggest:
- ask other people to test if the fix works for them too
- make a decision if documenting the fix would be beneficial
- maybe provide a .reg file to change the key
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1523>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADl57RSnLW7lvth_35Z6qNjWY5naXZwks5t1uyKgaJpZM4UMqfZ>
.
|
It's the very enlightening As said, this isn't a Virtualbox / Vagrant / VVV issue. All other browsers on Windows 10 work. Edge doesn't. I always had this problem also on another Windows machine. However, I really need to test on all browsers using different assistive technologies, and I guess other developers would like to test with Edge too. This fix is the only one that worked for me. I'm aware of the changes in core related to the build step, thanks 🙂 |
|
am i imagining this, i thought that edge worked before... if it didn't, no one actually tested Edge? now i really wanna go back to the previous state and test the older VVV 2.2.0 |
|
I always recommend using Browsersync for cross-browser testing ( After a simple setup (example here), just run |
|
@dingo-d thanks. As said, personally I need to test with all browsers using various assistive technologies (e.g. screen readers), and Browsersync doesn't help. |
|
Oh, yeah, in that case, this is a big issue. |
|
i did more test on this... because I usually install windows 10 on virtualbox and target 192.168.50.4/192.168.50.1 as a second adapter... It seems like if I were to install the SSL or non SSL and using Microsoft Edge, I can actually use it. see below
so it got me curious. what's the difference. |
|
so the image above is under VirtualBox running Windows 10 Pro and i didn't need to edit registry or anything like that, it just works under virtualbox windows 10, but the actual host. i just get, can't reach the page. |
|
give u better idea, now it says im using windows 10 Pro (Running) - Oracle VM VirtualBox |
|
@tomjn |
|
None, I don't know much about MS Edge |
|
It is still happening? we have to consider that the new versions of edge now use chromium engine. |
|
We'll see 🙂It's not related to the rendering engine. It's a Microsoft network "feature". |
|
so i tested the new Edge, its the same thing. |
|
What progress has been made on this? Is the provided workaround with editing the registry the only fix for now? Thanks for your help so far. |
|
i think the way to fix this is to edit the registry, can we document this in the documentations. |
ghost
mentioned this issue
|
Is this still an issue? Edge for MacOS appears to run fine:
|
As mentioned previously, this isn't related to the browser's engine. It's a Microsoft network "feature" that "works" only with Edge. Not sure how the new Edge will behave. |
|
can we have people test the new Edge on Windows? I have tested on 3 different computers with Windows 10 Home/Pro and it works fine. Since the new Edge is majority Chromium based |
|
Worth reminding WordPress supports the last 2 versions of major browsers, including the last 2 Edge versions.
|
|
I don't think that matters right now! The whole point right now is to have people test the new Microsoft Edge that is based on Chromium. If we can get people to test without problem on Edge even if there are some small issues, it can still display sites and which the whole point of this ticket. The new Microsoft Edge will be implemented into the Core of Windows 10 in the next version or two. @tomjn: I think we should just close this ticket because no one will use Edge as much as we should be doing testing on, but that's just me. |
|
Ah I was hoping that the new Edge might have bypassed this issue being Chromium based. The worst that happens is we end up with a less suboptimal situation, a little more info doesn't hurt |
|
I'll try testing this again at some point today hopefully. |
|
I just upgraded an old VVV environment from 2.2.0 to 3.3.0 and |
|
It does not work with a fresh VVV 3.3.0 install on Edge on Windows 10, It does work in IE and chrome. Dang you windows. Dang you. This is why I use linux most of the time for development anyways. Please let me know if I can be more helpful in testing. |
|
@jimboobrien @tomjn: this is why I open a new ticket with the latest URL to download the new Edge. if we continue here. no one is gonna know to download the new Microsoft Edge.
|
|
I am going to point out that when most of the people who are using Windows 10, you can download the new Microsoft Edge (https://www.microsoft.com/en-us/edge/), this update will replace the old Microsoft Edge that is the core of Windows 10. Please download and install the new Edge browser before making assumptions if it works or not. I have recently tested on 3 different Windows 10 systems and the new Microsoft Edge works without any configurations whatsoever.
|
|
Confirmed, once I upgraded Edge to newest version it does work in Edge now. I was on 44.1 I believe before I upgraded. |
|
Now that edge is based on webkit this ticket maybe can be closed as a lot of things are changed? |
|
@msaggiorato what do you think? I know you're on Windows at the moment |
|
closing |
Microsoft Edge has network problems, especially for unusual network stuff. It's impossible to see a VVV site in Edge. It's a known issue, just google for "Edge Hmmm... cannot reach this page" and you will find tons of reports and suggestions. 99% of them didn't work for me.
It's an Edge bug, nothing wrong with Virtualbox and VVV.
Eventually, I've found a solution but it requires to edit a Windows registry key, For people who need to test with all browsers, worth considering to document the fix. See this comment:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/10142843/#comment-8
For me, the path to the registry key was slightly different and ended with
\0016, I guess the commenter meant to search in any of the sub-folders that start with00. The key to edit is*NdisDeviceType(it really starts with an asterisk) and needs to be changed from 1 to 0.Being a registry edit, people should really know what they're doing, so in any case a registry backup, or bookmarking the key to easily find it again and revert would be highly recommended.
What I'd suggest:
.regfile to change the keyThe text was updated successfully, but these errors were encountered: