Why does Microsoft Edge open some local websites, but not others, where the domain name is routed to 127.0.0.1 in the hosts file

Question

Like many programmers, I test sites locally. I use the hosts file to map domain names to my local ip (127.0.0.1).

I use qualified domain names, usually with the subdomain "d" (for "development").

For example:

d.somewebsite.com d.anotherwebsite.com and so on... 

In Microsoft Edge, most websites work. However, some of them do not. There is nothing special or strange about domain names that won't work. Just plain d.someletters.com .

They work great in Chrome, IE, and Firefox.

An error message appears in Edge: "Hmm, we cannot get to this page."

At first I thought it was not an IP solution. However, I realized that when I made a typo on another unrelated URL, requests that were not redirected by the hosts file are sent to my ISP, which will be resolved. If my ISP cannot solve it, they will send a page with the results of special search queries with suggestions about what you are trying to find. Well, when I go to my local domain, I do not get this page from my Internet provider. I get the error mentioned above right from the edge.

So, it seems to me that Edge resolves the domain correctly, otherwise it would be sent to my ISP DNS server.

So, I would think that maybe Edge just can't connect to the local machine. But, as I said, some of these local domains work fine. In addition, 127.0.0.1 works directly in Edge. These are just a couple of domain names that give me a problem. And only in Edge (all other browsers work) Any ideas?

Apache2 web server for Windows (xampp), if that matters.

Also, if I open the debug window in Edge and monitor the network, I don’t see any requests at all.

EDIT: I no longer use the hosts file. I have dnsmasq running on one of my Linux boxes, and I use it for DNS instead of hosts. Also, you are not using loopback (obviously, since DNS is in a different window now), I am using the internal private IP address (192.168 ...). Same problem.

Answer 1

• Your network may block the loop as a security measure in Windows 10.

• Open a command prompt as administrator and run this command to exclude Edge from reverse loops:

   CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe" 

( Microsoft.MicrosoftEdge_8wekyb3d8bbwe is an Edge application identifier)

There is a blog entry here for more information: https://blogs.msdn.microsoft.com/msgulfcommunity/2015/07/01/how-to-debug-localhost-on-microsoft-edge/

Answer 2

I (thought I) decided this!

Things that didn't work:

• Modify IE Compatibility Settings or Windows Compatibility Lists
• Using FQDNs
• Using a non-loopback IP address
• using http vs https
• remove all javascript and cross-site scripts / resources from the web page
• check / uncheck the box about: flags to enable localhost feedback or use compatibility settings
• delete / add / edit entries in TabProcConfig windows registry
• delete browsing history, cache, cookies

Solution: completely illogical:

Remove domain names from the list of trusted sites!

1. Open the Internet Options dialog box (just ask Cortana or use windowskey + s)
2. Go to the Security tab
3. Click on Trusted Sites Zone
4. Click the Sites button
5. Remove problem domain names from the list of trusted sites
6. Click Apply, and then close the dialog box.
7. Open Edge (or restart it if it is already running)
8. alto

I must note that, based on common sense, I decided that the reason for the problem was not only the fact that the site was simply present in the Trusted Sites zone. I thought it was some kind of situation in this zone. So, before removing the domain names from the list of “sites”, I made all the settings exactly corresponding to the settings of my Internet zone (medium level of security, enable secure mode, no server verification is required for all sites), and I also tried any other combination I could find. There was no combination of security settings for the zone that worked. The only solution was to completely remove the domains from the list of trusted sites. The funny thing is that it works in IE no matter although it is a dialog box for Internet settings for IE. This seems to only affect Edge.

EDIT: Two weeks later, I change my configuration to use dnsmasq on the local Linux machine and use it for DNS instead of the hosts file. I'm not sure if this happened right away, but at some point Edge stopped working again! I already had the "allow loopback" about: flags flag checked, so I did not expect the CheckNetIsolation patch to work. But it is so. Edge version 20.10240.16384.0. I used the patch from I can’t open localhost in Microsoft Edge (Project Spartan) in Windows 10 Preview

EDIT # 2 A couple of months later, and Edge had this problem again. I tried both of the previous solutions (and others) and none of them work for me anymore. I leave this answer because I assume that I had two separate problems.

Answer 3

Edge does not support VPN IP addresses, so you need to use some kind of proxy server in any workaround. Here are some of the solutions I found:

• Install and run fiddler . Fiddler will basically intercept the request from the browser and then redirect it to the destination. This is the easiest workaround.

• Configure the proxy server through the built-in Windows tool: netsh . The main steps include assigning your development domain to an available local private IP address in the range 127.0.0.0/8 , and then mapping this IP address to the IP server in the VPN. See step-by-step instructions here.

• Use the port forwarding feature for ssh to configure the proxy. Assuming port 80 is available on the local host, add 127.0.0.1 d.somewebsite.com to your host file, then run the following ssh command: ssh -L localhost:80:localhost:80 user@devwebserver , where devwebserver is your hostname development web server (for example, in a virtual or vagrant instance or through a VPN). This option assumes that you have ssh access to the dev server.

Answer 4

The “remove from trusted sites” solution does not work for me because my local sites were not on my trusted sites.

But you made me look at the Internet settings, and I managed to get IIS to work on local sites for me in Windows 10. This is what I did:

• Open Internet Options and select Local Intranet

2. Click Sites

3. Click Automatically Detect Intranet Network

4. Click OK. Try your local site in Microsoft Edge and it should work now.

Answer 5

May not apply to your situation, but nonetheless. My setup was as follows. The public space (Internet) address page tried to load the page with the private space address (intranet) in the iframe, and Edge refused to load the intranet page with the same message "Hmm, we can not get to this page", and with "Error SEC7117" in the console debugging. Turns out Edge doesn't like to mix Internet zones and intranets (for reasons, see Understanding Blog in Advanced Protected Blog). Edge launches tabs in individual AppContainer, and AppContainer network restrictions depend on your network configuration.

My solution was to pull out the server that hosted the intranet page in question from the domain network, assign it a second private IP address, and create a second DNS record for that IP address. The server ultimately has 2 IP addresses: one on the domain network and one alternative and 2 different DNS records. Edge then points to the alternate URL and starts loading the intranet page normally. It seems that if the IP masks of the PC and the URL of the page do not match, Edge will load the page.

The blog post I mentioned has information about Loopback blocking for localhost and the lack of privateNetworkClientServer in IE. As far as I can tell, all this information refers to Edge.

Answer 6

When this happens to me, I can find the domain entry in the registry section below that corresponds to the domain. When I delete, everything works, for a while ... I don’t know why, but Edge will add it in the end.

Computer \ HKEY_USERS \ S-1-5-21-964789662-521690395-1734141374-1111 \ Software \ Classes \ Local Settings \ Software \ Microsoft \ Windows \ CurrentVersion \ AppContainer \ Storage \ microsoft.microsoftedge_8wekyb3d8bbwe \ MicrosoftEdge \ TabProcConfig

Answer 7

None of the other solutions worked for me. Turns out my problem is with the VPN. Microsoft Edge still does not support VPN IPs, while Internet Explorer 11 does. It is impressive that this is still a problem since May 2016.

Additional information: https://social.technet.microsoft.com/Forums/en-US/b3a687ae-345d-4c3f-9070-184b33fb1fc6/microsoft-edge-cant-access-vpn-ip-address-but-ie-11 -can? forum = win10itprogeneral

Microsoft Edge currently does not work with VPN. And Microsoft Edge’s Internet connectivity mechanism is slightly different from Internet Explorer 11 and other desktop browsers, which I can’t explain, since I know little about it.

So, based on the current situation, use Internet Explorer 11 instead.

Answer 8

In my case, changing the type of network from private to public has done its job. This is also reproducible, and changing the network type reliably changes the state from "running" to the following: Http failure response for (unknown url): 0 Unknown Error

Answer 9

Based on your edits, you access the site at 192.168.0.0/16, and not at 127.0.0.1. I assume that you have a problem with the behavior of the Edge browser in different ways depending on the interface used for access. website. Other browsers I tried do not behave this way.

In my environment, I had a network setup only for the Virtualbox host, and NdisDeviceType was 1. Edge would only allow me to go to sites through this interface after I changed NdisDeviceType to 0. The registry key you need is:

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\XXXX 

Instead of XXXX, you need the correct key for your interface, which I determined from the "print route" and subtracted 1. For me it was "0016".

The value for the change is called *NdisDeviceType . (This is a literal asterisk.) I changed it from 0 to 1, and I had to restart Windows to notice this change.

My answer was received from a Jani L post dated October 3, 2017. I have also posted this solution in more detail at https://stackoverflow.com/a/166252/ ... Also see Virtualbox Ticket 15565 .

Answer 10

For me, I went to Internet Options (control panel), then Security, then the selected local intranet, and then put a checkmark in Automatically detect intranet network. In this case, the greyed nested parameters are lower, and Edge immediately started using my hosts file.

Answer 11

Something similar happened to me, I just reset the network from the network settings page and restarted my computer, and everything that was back to work, as it was before.