Can't access 127.0.0.1 [closed]

Question

I can't figure out when this started to happen, but the result is - 127.0.0.1 is not working on any port from anywhere (for example, browser says Unable to connect). Here are the results of my research:

1. localhost, COMPUTER_NAME and actual IP address all work fine
2. there is nothing special in my hosts file
3. ping to 127.0.0.1 and tracert do work fine
4. all the programs that have 127.0.0.1 hardcoded are not working (this point makes me disappointed the most, because I can't do anything in this case )

What else can I do to identify the source of problem and fix it?

UPDATE: as soon as Redis does work on 127.0.0.1 and both IIS and AzureStorageEmulator don't work I assume this is HTTP only issue.

Answer 1

Just one command did the work

netsh http add iplisten 127.0.0.1

Answer 2

If it's a DNS problem, you could try:

• ipconfig /flushdns
• ipconfig /registerdns

If this doesn't fix it, you could try editing the hosts file located here:

C:\Windows\System32\drivers\etc\hosts

And ensure that this line (and no other line referencing localhost) is in there:

127.0.0.1 localhost

Answer 3

In windows first check under services if world wide web publishing services is running. If not start it.

If you cannot find it switch on IIS features of windows: In 7,8,10 it is under control panel , "turn windows features on or off". Internet Information Services World Wide web services and Internet information Services Hostable Core are required. Not sure if there is another way to get it going on windows, but this worked for me for all browsers. You might need to add localhost or http:/127.0.0.1 to the trusted websites also under IE settings.

Answer 4

I had a similar issue. Check your listen port. A mistake I made ealier was

app.listen(() => console.log(APP_NAME} is listening on port ${PORT}`))

Make sure you include the port as shown below

app.listen(PORT, () =>{
  console.log(`${APP_NAME} is listening on port ${PORT}`)
})

Answer 5

In the end for us, it was IE11 that was blocking for 127.0.0.1 - after adding it to the exceptions list, it loaded the page.

Answer 6

This answer may seem overly obvious, but in most cases it is sufficient to simply remove the "localhost" entry in the "Host Name" field: