Localhost refused to connect Visual Studio

I have copied my solution file from another system and tried to run it on my machine: For this, I have gone to the project folder and deleted the previous solution file and copied the new one.

Now, it started giving me error. connection refused etc. So, I got one solution from here: How to solve ERR_CONNECTION_REFUSED when trying to connect to localhost running IISExpress - Error 502 (Cannot debug from Visual Studio)?

According to it, I changed the port number from 1049 to 1052. It loaded and one of the pages gets loaded. But when I entered the desired login credentials then it redirected to the older port again, like this:

http://localhost:1049/Home/SearchFlight

and the error is:

 This site can’t be reached

 localhost refused to connect.
 Search Google for localhost 1049 Home Search Flight
 ERR_CONNECTION_REFUSED

Now, I don't know what to do from here. I have changed the port number to 1052 but still its pointing to 1049. What should i do now?

asked May 20, 2016 at 17:32

I had a similar issue. Try this and it should work

  1. Go to your project folder and open the .vs folder (keep your check hidden item-box checked as this folder may be hidden sometimes)

  2. In the .vs folder open the config folder

  3. See that applicationhost.config file there? Delete that thing. (Do not worry it will regenerate automatically once you recompile the project.)

Localhost refused to connect Visual Studio

SharpC

6,4984 gold badges45 silver badges39 bronze badges

answered Aug 12, 2016 at 21:12

KushKush

1,3371 gold badge8 silver badges3 bronze badges

9

Usually on local machine we are getting errors like This site can't be reached localhost refused to connect because we have self signed certificate configuration broken for local IIS Express. Sometimes it happens when you change URLs in launchSettings.json or never configured self signed certificates on this machine at all.

To fix self-signed certificate on the local machine you need to: 

  1. Delete .vs folder (requires to close Visual Studio 2017)
  2. Run these commands in cmd As Administrator:

    cd "C:\Program Files (x86)\IIS Express"

    IisExpressAdminCmd.exe setupsslUrl -url:https://localhost:12345/ -UseSelfSigned

  3. Make sure you run VS2017 As Administrator and check if the issue addressed

Note: https://localhost:12345/ is what is in your launchSettings.json for HTTPS

Localhost refused to connect Visual Studio

Natrium

30.4k16 gold badges59 silver badges73 bronze badges

answered Sep 11, 2018 at 17:49

Dmitry PavlovDmitry Pavlov

29.5k8 gold badges100 silver badges117 bronze badges

6

Changing port number has resolved the issue

Localhost refused to connect Visual Studio

answered Feb 17, 2017 at 12:45

Localhost refused to connect Visual Studio

4

Just Delete the (obj)Object folder in project folder then Run the application then It will work fine. Steps:

  1. Right Click on the project folder then select "Open folder in file Explorer".
  2. Then Find the Obj folder and Delete that.
  3. Run the Application.

answered Dec 21, 2016 at 10:59

Localhost refused to connect Visual Studio

1

Unfortunately, none of these answers worked for me. This answer finally did for Chrome only. Unfortunately, you have to do it each time:

  1. Open this in your browser: chrome://net-internals/#hsts
  2. Go to Delete domain security policies
  3. Enter "localhost"
  4. Restart browser

Google Chrome redirecting localhost to https

answered Sep 19, 2018 at 17:59

ShaneShane

4,1057 gold badges45 silver badges64 bronze badges

2

I had the same problem. Deleting .vs folder (including all contents, folder might be hidden) worked for me.

answered Feb 20, 2018 at 14:30

Localhost refused to connect Visual Studio

Baqer NaqviBaqer Naqvi

5,4543 gold badges45 silver badges66 bronze badges

1

I solved a similar problem by listing bound IP addresses in a cmd window running as admin:

netsh http show iplisten

Then, one by one, blowing them all away:

netsh http delete iplisten ipaddress=127.0.0.200
netsh http delete iplisten ipaddress=127.0.0.2
...

answered Jun 7, 2017 at 22:06

WatusimotoWatusimoto

1,7291 gold badge22 silver badges36 bronze badges

1

In my case, I need to update "publishAllPorts" = false in .Net 5 MVC project's launchSettings.json.

 "Docker": {
      "commandName": "Docker",
      "launchBrowser": true,
      "launchUrl": "{Scheme}://{ServiceHost}:{ServicePort}",
      "publishAllPorts": false
    }

answered Sep 2, 2021 at 20:35

Localhost refused to connect Visual Studio

ChinaHelloWorldChinaHelloWorld

1,0071 gold badge12 silver badges6 bronze badges

2

I ran my Visual Studio as "Run as administrator" and this solved my problem.

answered Dec 27, 2018 at 15:18

anuanu

2951 gold badge4 silver badges14 bronze badges

1

If found it was because I had been messing about with netsh http add commands to get IIS Express visible remotely.

The symptoms were:

  • the site would fail to connect in a browser
  • the site would fail to start (right click IIS Express in the Taskbar and it was missing)
  • if I ran Visual Studio as admin it would start in IIS Express and be visible in the browser

The solution was to list all bound sites:

netsh http show urlacl

then delete the one I had recently added:

netsh http delete urlacl url=http://*:54321/


In addition I had removed localhost from the hidden solution folder file .vs\config\application.config for the site:


    

so had to put that back:


    

answered May 15, 2020 at 7:40

Localhost refused to connect Visual Studio

SharpCSharpC

6,4984 gold badges45 silver badges39 bronze badges

1

This happened to me in VS2017 v 15.6.7 using .net core 2.0.

When the project first launched it created an SSL Cert for localhost and started fine. When I disabled SSL I kept getting this issue.

Apparently when you disable SSL the port numbers are changed and not all of the port numbers get changed to the new port. Make sure port numbers on Debug are all the same number.

Localhost refused to connect Visual Studio

answered May 2, 2018 at 20:05

Localhost refused to connect Visual Studio

Donny V.Donny V.

21.5k13 gold badges64 silver badges79 bronze badges

0

I was having this issue and solved it by closing all open instances of Visual Studio.

answered Jun 6, 2018 at 17:48

R. SalisburyR. Salisbury

1,89515 silver badges16 bronze badges

1

Go to control panel > Programs and feature > IISExpress > Repair

answered Mar 6, 2020 at 6:47

RonRon

1,8314 gold badges18 silver badges35 bronze badges

3

Open cmd as administrator and run this command:

netsh http delete iplisten ipaddress=xxx.xxx.x.xxx

ipaddress is your private ip.
This worked for me.

dferenc

7,80712 gold badges42 silver badges48 bronze badges

answered Jan 28, 2018 at 11:47

Localhost refused to connect Visual Studio

I faced this annoying problem all the time in my Visual Studio MVC application especially when you start your work in the morning. Many solutions in this thread works sometimes; but there were many times none of this solves my issue.

At last I figured out only a combination of these steps works for me. Hope this helps somebody.

  1. Close VS.

  2. Delete .vs folder under your solution. Don't worry, it will be automatically created when you open the solution again.

  3. Delete bin and obj folders.

  4. Delete your cookies from the browser that you use to debug the application.

  5. Delete the *.csproj.user file located in the project folder.

  6. Open your startup project file (*.csproj) in Notepad++ or your favorite editor. Go towards the end of the file and delete below 3 lines that contains the local development port info. Don't worry it will be recreated on running the solution again.

      0
      /
      http://localhost:60573/
    
  7. Open your solution again, clean, build and run it. You should be good to go. If this don't work, restart your machine after step 6.

answered Oct 5, 2021 at 14:16

RenjiRenji

796 bronze badges

For this to work for me, all I had to do was recreate the virtual directory. I had re-installed Windows and then pulled the project back out of Git. To do this, right-click on the solution project and choose Properties, then go to the Web tab and click the Create Virtual Directory beside the Project Url.

I hope this helps someone else too!

Bud

answered Feb 21, 2017 at 13:51

Project properties> Web > Create Virtual Directory worked for me

answered May 8, 2017 at 15:07

Right Click on Project >> Properties >> Select Web Tab >> Under server Select "Use Visual development server" so indirectly it will uncheck "Local IIS Server"

Hope so it may resolve this issue.

answered Aug 28, 2017 at 8:25

Change the port number and remove script debugging (if enabled) to resolve in localhost.

Localhost refused to connect Visual Studio

smonff

3,3163 gold badges39 silver badges46 bronze badges

answered Aug 16, 2018 at 17:43

I've tried everything but nothing worked, but this did. If you can debug on local IIS instead of Express, change the configurations as shown in the image below. Do not forget to click on "Create virtual directory"

Localhost refused to connect Visual Studio

answered Aug 29, 2018 at 19:55

Localhost refused to connect Visual Studio

rebooting the machine was the only thing that worked for me

answered Dec 17, 2018 at 14:24

Fabio NapodanoFabio Napodano

1,1591 gold badge14 silver badges17 bronze badges

1

I recently ran into this exact problem and tried most of the suggestions but it turns out my problem was something different.

Our application has a section that redirects you to HTTPS if you are on HTTP (yes, I know there are better ways but this is legacy). In addition, there is special handling of localhost when you are in dev mode which redirected you back to HTTP, though I don't know why.

I have a new requirement that requires testing in HTTPS.

On a normal web page, changing http:// to https:// and calling Redirect would work fine but in IISExpress you are using custom ports. So for example, if you are on https://localhost:44300 you can't just switch to http://localhost:44300 b/c that port only serves https, not http.

So, if you are having this problem and you've cleared the config files and it didn't help, check your code for redirects. you might have something using a hardcoded or partially hardcoded url or a url from a config file that you haven't updated to https.

Update: I also suggest clearing all .suo and .user files and someone else suggested clearing the obj/ folder. I suggest doing this with VS closed and then restarting. I had a lot of trouble with values for ports being cached when i tried to setup https:// and change ports. I also suggest trying this suggestion to check that the SSL port is within the correct range, though I don't know if that is still a requirement https://stackoverflow.com/a/24957146

answered Jan 7, 2019 at 20:22

Localhost refused to connect Visual Studio

ZackZack

2,2112 gold badges21 silver badges37 bronze badges

In my case, Visual Studio 2017 > Tools > Options

In Debugging menu in the side list find Edit and Continue

Uncheck the Enable Edit and Continue check box

This resolves my problem.

answered Jan 25, 2019 at 10:39

Localhost refused to connect Visual Studio

Nilay MehtaNilay Mehta

1,5822 gold badges18 silver badges26 bronze badges

Same problem here but I think mine was due to installing the latest version of Visual Studio and having both 2015 and 2019 versions running the solution. I deleted the whole .vs folder and restarted Visual Studio and it worked.

I think the issue is that there are multiple configurations for each version of Visual Studio in the .vs folder and it seems to screw it up.

answered May 8, 2019 at 18:12

Localhost refused to connect Visual Studio

tqrecordstqrecords

5221 gold badge5 silver badges20 bronze badges

Sometimes https and http ports can be same because if two tags are given same ports IISExpressSSLPort and DevelopmentServerPort Make sure these two ports have different ports then in IISUrl use your default port either HTTP or HTTPS

https://localhost:44365
  • For HTTPS Use IISExpressSSLPort
  • For HTTP Use DevelopmentServerPort

Then you may delete hidden .vs folder in solution folder

answered Oct 28, 2019 at 6:00

Localhost refused to connect Visual Studio

Ali JamalAli Jamal

82411 silver badges18 bronze badges

Try deleting cookies for your localhost

Localhost refused to connect Visual Studio

answered Nov 20, 2019 at 10:23

Localhost refused to connect Visual Studio

My problem turned out to be a property which called itself:

Localhost refused to connect Visual Studio

Once I fixed this, the misleading connection error message disappeared.

answered Apr 16, 2020 at 9:08

Andy BrownAndy Brown

5,0894 gold badges32 silver badges37 bronze badges

0

None of these solutions worked for me. I'm not 100%, but I think my issue might have been with running the same project on the same port from multiple branches. That used to be an issue for me on Local IIS --- I'm not sure if that's also an issue on IIS Express. What worked for me was following this solution:

https://stackoverflow.com/a/27033934/2133723

Which says to go to:

File -> Open -> Web Site...

and remove the relevant projects. After this, I was able to run the project without changing the port.

Prior to doing this, I had followed the other solutions posted on this question (which didn't help me), such as deleting the .vs folder, so I'm not sure if that would be a necessary step prior to removing the website from File -> Open -> Web Site....

answered Feb 11, 2021 at 20:56

EmilEmil

1,08112 silver badges23 bronze badges

Like Donny V. this happened to me in VS2017 using .net core 2.0.

When the project first launched, VS displayed a dialog, offering to create an SSL Cert for localhost - but I didn't want to use SSL, so I stopped running and went into Project Properties and disabled SSL (a checkbox that can be cleared). After doing that I kept getting the issue described.

After trying many things what actually resolved the issue for me was editing the launchSettings.json file located under [ProjectName]/Properties - it's accessible from Solution Explorer.

When the editing was complete, the contents looked like this (where 12345 is a Port Number, and where MyNETCoreApp is the name of the project).

{
    "iisSettings": {
        "windowsAuthentication": false,
        "anonymousAuthentication": true,
        "iisExpress": {
            "applicationUrl": "http://localhost:12345/"
        }
    },
    "profiles": {
        "IIS Express": {
            "commandName": "IISExpress",
            "launchBrowser": true,
            "launchUrl": "http://localhost:12345/",
            "environmentVariables": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            }
        },
        "MyNETCoreApp": {
            "commandName": "Project",
            "launchBrowser": true,
            "environmentVariables": {
                "ASPNETCORE_ENVIRONMENT": "Development"
            },
            "applicationUrl": "http://localhost:12345/"
        }
    }
}

The edits I made were:

  • Updated the Port Numbers so they were all the same number
  • Removed a key:value of ssl:0 in one spot
  • Updated all https:// instances to be http://

answered Jul 14, 2018 at 6:07

I had to add https bindings in my local IIS

answered Aug 24, 2018 at 17:40

Th4t GuyTh4t Guy

1,4423 gold badges16 silver badges28 bronze badges

Why does localhost refuse to connect?

The localhost simulates a web server running on your computer. When the “localhost refused to connect” error appears, it is likely due to misconfigured port. Other common reasons include insufficient permissions and the Apache webserver not running properly.

Why is 127.0 0.1 refused to connect?

0.1 (loopback address). So your client is trying to connect to any of the non-loopback addresses of your machine, while your server is listening only on the loopback address . So, no connection can be established. The solution to this problem is that connect to the same end point your server is listening on.

What does Connection refused mean?

A Connection Refused (IP Address) error occurs when: You use the wrong IP address in the connection string. Use the database's private IP address in the connection string and try to connect from a Droplet that isn't allowed to access the VPC network.