asp.net waiting for localhost forever

Question

Suddenly this morning I turned on my computer and launched visual studio... And no matter what I tried and whether I run or debug, and whatever the browser is ( chrome / fir

Answer 1

Okay, I've found that this happens (on a server) when you've hardened security properly.

For example, you no longer blanket apply IIS_IUSRS to the wwwroot but setup proper accounts for each App Pool and are setting the NTFS perms properly.

The problem is that the worker process/ASP.NET wants to enumerate the files in the folders "leading up to" your website root. I think it wants to look for web.config files etc.

The failure to produce an error, i.e. the infinite loading is a bug in my opinion.

e.g. i:\wwwroot\project\virtual\base

You'll need to apply IIS_IUSRS group read access to wwwroot, project, virtual but not base. The trick is to only apply to the current folder, i.e. don't apply to subfolders and files.

Apply read rights just to the worker process/AppPool identity to the base folder.

If IIS_IUSRS has read rights to the whole tree, then all worker processes will have read access to all other website base folders and contents, such that a compromised site will be able to access data/config in other sites.

Answer 2

For me, on aspnet core it was a problem in Configure() method hanging because of exception

Answer 3

Check firewall for blocked ports, change dynamic ports of application to some fixed port.

Answer 4

My issue was a result of a not having proper credentials on the working website folder. If you arent sure grant full control to the folder as a test. User = IIS AppPool[app pool name]

Answer 5

Sometime it happens due to issue with symbols loading. Try this

Go to Tools -> Options -> Debugging -> Symbols and click the button 'Empty Symbols Cache'

Answer 6

I had a similar issue where my site got "Waiting for" forever. Tried restarting the website and nothing.

I was not able to reboot the machine (I am pretty sure that it would solve) so I kept investigating what could be.

I found out that, in my case, the solution was to change the "Application Pool" of the website. It appears that the current one crashed or something like that (I was able to stop it but not start it back again), so I created a new Application Pool and the site started working again.