Windows 10: Edge browser can't access LOCALHOST type of IP addresses (build 10122

Hi there

same problem with EDGE (the new browser) - can't access localhost type of addresses. I use several media servers with Web interface for controls etc.

Get around - use loopback adapter -- but why should I -- Chrome / FF / IE all work still).

I don't want to use different browsers for different applications.

Cheers
jimbo

:)

 

Cannot access local server via local ip in Microsoft Edge

This is completely a windows issue. You can't blatantly deny this problem as a non-windows issue. As far as I understand this is to do with the way Windows Apps are designed to connect to the internet.

I'm facing the same issue accessing local ip addresses (for local servers on the network) through Microsoft Edge, whereas the same address works on other browsers. I checked the "about:flags" and the localhost loopback is allowed.

Could anyone suggest a solution to this?

 

Missing network protocol

I am in the process of building a Server - PHP - MySQL base for developing Webpages as .php files. I need to use the 'localhost' to view my pages. If I open any browser (I have Edge, IE11, Firefox, Chrome, and Opera) and type in http://localhost/ I find
I cannot connect. On running a troubleshooting sequence the error message displayed is 'missing network protocol'.

I ran 'netsh int ip reset' on an elevated command prompt to try and fix this issue.

The result was this:

C:\>netsh int ip reset

Resetting Global, OK!

Resetting Interface, OK!

Resetting Unicast Address, OK!

Resetting Neighbor, OK!

Resetting Path, OK!

Resetting , failed.

Access is denied.
Resetting , OK!

Restart the computer to complete this action.

C:\>

The problem of a missing protocol was not fixed.

Can anyone help me with this problem? My thanks, .

 

Why do you keep creating new posts about this for every new release? This is not something that's going to change, it's an inherent security feature of Universal applications that they can't access localhost, and Edge is a Universal application.

I repeat. This isn't going to change.

 

Hi there

I must then have mis-understood the whole idea of the Edge Browser -- We were led to believe that IE will be replaced by Edge -- if that is indeed the case then for some people they won't have access to a properly fully functional browser.

So what IS Ms's intention regarding the future of IE -- is it to be retained or to be replaced.

That's where my confusion is coming from -- if IE IS to be retained then OK I'll do WITHOUT edge -- but if IE is going to be replaced then I want a browser that doesn't LIMIT the functionality I already have.

If EDGE won't handle LOCALHOST -- then that's fine so long as alternatives are available -- the mis-understanding came from the fact that I (and I'm sure I'm not the only one) who thought that Ms was giving up on IE which would be replaced by EDGE.

Cheers
jimbo

 

Does it make any difference if you put your local IP in instead of using localhost

for accessing my media servers I use http://xxx.xxx.xxx.xxx:xxxx, or does this just auto translate to localhost when entered

 

Hi there

the addresses 127.0.0.1 don't work either -- the only way around the whole problem is to use some type of loopback adapter if you must use edge.

I'm sure this restriction will be of significance to some users -- I don't know about "Universal Apps" or whatever they call it now but surely some type of firewall or other config setting could fix this problem. I have several media servers all controlled via a WEB interface.


cheers
jimbo

 

I think that if someone is going to test Edge for a website that they could have a hosing service to set the site up on and use that to test it out?? Since Edge is an app and not a pure browser I don't know it the local hose option will ever be available.

 

I was meaning the actual IP address of your machine with the media server on it, even if your are on the machine

eg
http://192.168.0.10:8960

 

Hi there

No go I'm afraid. Same error

Cheers
jimbo

 

That's a shame *Sad

I will have the same problem as you with Edge as that's how I access my media browsers

 

IE will not be going away, at least any time soon. Edge is an entirely standards compliant browser, and has *zero* backwards compatibility for older browser support, as such IE will be required to be around as a backup for some time to come for sites that just won't work with a fully standards compliant browser with no backwards compatibility.

Edge will be the default browser, by default. But IE is still there, it's just hidden away in the start menu.

 

Hi there

Thanks for clearing that up.

If IE will still be around for a while then that's fine.

Cheers
jimbo

 

I'm glad I found this thread as I too thought IE 11 was not going to be in Windows 10 release version. I use a local proxy that I will never give up. My other browsers have zero problems with connecting through my local proxy. Spartan cannot do so even though it has the settings to set up a local proxy connection. It lets me set up my local proxy connection but then says it can't connect and suggests the problem is likely my firewall. Why are those settings there if it can't use them?

Based on this craziness, I probably will simply stay with Windows 8.0 Pro. I am doing Win 10 Preview on Hyper-V virtual machine to see if I will want to upgrade to it but evidently it would be a downgrade if Spartan is so badly crippled that it can't connect to a local proxy. My browsers of choice are all Gecko based so I seldom use IE and wouldn't use Spartan much at all but I would not want Windows 10 if IE is hidden and its future is uncertain as IE has to be used at first setup to download Fx or Pale Moon and occasionally IE has to be used on Microsoft sites and my airlines site and some others that are setup only for IE. My airlines has a new site in beta and it works only with IE as does its current website. Microsoft is cutting its nose off making the future of IE 11 on Windows 10 uncertain since it wants everyone on Windows 10 and that won't happen if only Spartan and no local proxy is available.

This is the first I have heard that browsers like Fx, Sea Monkey, Pale Moon, etc are not standards compliant. They have been always standards compliant yet they have no problems with a local proxy connection. Spartan should have no problems either.

 

You misread. I did not say other browsers were not standards compliant. I said, Edge was ONLY standards compliant, and was not backwards compatible with older (non-standard) browsers. So websites that require IE8 compatibility will not work in Edge (one of the reasons the TenForums software has such problems with Edge is that it requires IE9 compatibility for Microsoft browsers, and it is trying to serve up IE9 compatible content to Edge).

Firefox, Chrome, etc.. are standards compliant, but they are also backwards compatible. Edge is not.

IE11 is not "uncertain" It will be in WIndows 10 for the foreseeable future. It just won't be the default browser, by default.

And i'm sorry, but any company making new sites that require IE today are the ones cutting their own throat...