Note that this address worked just fine in Google Chrome, Internet Explorer 11 etc.ġ. This site was hosted by a web server running in my VM guest. I couldn't access addresses from my Edge on the VM host suchĪs. I have a host-only network for my VM guests. In my case, I have VirtualBox 5.2.18 running on Windows 10 build 1803 "Spring Creators Update". CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe" Control panel, Network and Internet, Internet Options, Security and adding my site explicitly to Trusted Sites or Local Internet.ģ. Using about:flags and confirming that "allow localhost loopback" was onĢ. I tried various suggestions above but I couldn't find one that worked for me. But at least I can now go on with developing. I have obviously not added the previous entires manually in the past, so I have no idea what is really going on. I added a few which didn't and lo and behold, they now load as well. I went to the registry key mentioned above and what I found was that all the sites that did load were in that list. So, while I could still reach 192.168.0.1Īnd 192.168.0.9 over https as well as 192.168.0.150, 192.168.0.252, 253, 254 and so on over http it just showed a generic "Hmmm.can't reach this page" message for the newly added 192.168.0.136 as well as an older Raspberry Pi running I have a bunch of local websites running on IoT devices and all of a sudden Microsoft Edge wouldnt allow me to open newly added devices (it worked in IE11 and Chrome though.). I have no idea why it even added the entry. Hope this might help somebody else with the same problem. I deleted the entry matching my IP address and it started working again. Apparently, Edge had decided to blacklist my local IP address.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |