Visual Studio “No connection could be made because target machine actively refused it 127.0.0.1:8888”

Question

I tried to run a solution through Visual studio on my local machine. I get the webpage to appear and receive the error on the page: Unable to connect to the remote server No con

Answer 1

I had this issue when I changed the configured port number for my website. The first run on Firefox or Chrome would work, but the error would appear in the Output window on subsequent runs and the page would never load. It seems the browser holds on to the port number after the debugging stops, so it cannot launch again.

The solution for me was to start running it in Internet Explorer. That is the one browser that consistently opens and closes the port appropriately in tandem with VS2013.

Answer 2

I know this is old but I would like to share what did to resolve this problem. I found out that the cause of this is from the Internet Explorer's Proxy connection is enabled.

You can go to IE > Settings > Internet Options

Then Internet Options dialog will open.

Go to Connections tab and look for LAN settings.

From there, if you see the "Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections)." checked, uncheck it and press OK.

then that error will be removed.

I hope this helps on other readers experiencing this kind of issue.

Answer 3

I had this problem due to a Fiddler upgrade. I just unticked "Enable IPv6".

Answer 4

Also check machine.config under

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config and/or C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config

i had this set by fiddler:

<system.net>  
    <defaultProxy>
        <proxy autoDetect="false" bypassonlocal="false" proxyaddress="http://127.0.0.1:8888" usesystemdefault="false" />
    </defaultProxy>
</system.net>

remove this xml part. If it does not take effect restart your computer (i needed it in my case).

Answer 5

For whom live in IRAN: you need to turn on your Proxy/VPN server.

Answer 6

I had same problem. It was configuration to point to Fiddler. I removed the fiddler configuration in the web.config file and problem solved.

<defaultProxy enabled="true" useDefaultCredentials="true">
  <proxy autoDetect="false" bypassonlocal="false" proxyaddress="http://127.0.0.1:8888" usesystemdefault="false" />
</defaultProxy>