Connecting to Visual Studio debugging IIS Express server over the lan
Solution 1
Update
I made a video that better describes the process, https://youtu.be/5ZqDuvTqQVs
If you are using Visual Studio 2013 or above, make sure you run it as an administrator for this to work.
Open the
%USERPROFILE%\My Documents\IISExpress\config\applicationhost.config
(in VS2015 it may be $(solutionDir)\.vs\config\applicationhost.config
) file. Inside you should see something like this:
<site name="WebSite1" id="1" serverAutoStart="true">
<application path="/">
<virtualDirectory path="/" physicalPath="%IIS_SITES_HOME%\WebSite1" />
</application>
<bindings>
<binding protocol="http" bindingInformation="*:8080:localhost" />
</bindings>
</site>
Change the bindingInformation=":8080:localhost"
to bindingInformation="*:8080:*"
(the port number, 8080 in my case, will differ.)
Note: If it does not work try with bindingInformation="*:8080:
the asterix can be removed.
Then make sure your firewall is allowing incoming connections on that port. You may need to restart the system or at least Visual Studio to get IISExpress to reload the config file.
If this doesn't work, take a look at this answer: https://stackoverflow.com/a/5186680/985284
Solution 2
VisualStudio 2015 Non-Admin
-
In your solution dir, in the file
.vs\config\applicationHost.config
change the line<binding protocol="http" bindingInformation="*:44302:localhost" />
to
<binding protocol="http" bindingInformation=":44302:" />
(where 44302 is your port)
-
From an admin command prompt:
i. Enable non-admin to bind to port
netsh http add urlacl url=http://*:44302/ user=Everyone
ii. Allow through firewall
netsh advfirewall firewall add rule name="IISExpress visualstudio app" protocol=tcp localport=44302 dir=in action=allow
- Start debugging from VisualStudio
Solution 3
Except to modify the iisexpress configuration file, sometimes you also need to run the command like below.
netsh http add urlacl url=http://*:49419/ user=Everyone
Solution 4
How to avoid running Visual Studio as an administrator
Using both Garret's and @shangkeyun's answer you can achieve connecting to the running website without needing to run Visual Studio as an admin user:
- Open
%USERPROFILE%\My Documents\IISExpress\config\applicationhost.config
- Search for your site using
name=MySiteName
- Duplicate the existing
<binding>
item in the<bindings>
section. You should now have two lines withbinding
. - Remove the "localhost" part in bindingInformation.
-
It should now look like this, assuming the port is
12345
:<binding protocol="http" bindingInformation="*:12345:localhost" /> <binding protocol="http" bindingInformation="*:12345:" />
-
Enable non-admin to bind to port
netsh http add urlacl url=http://*:12345/ user=Everyone
EDIT 2019: gregmac added a step to whitelist the VS instance. I never needed this, but listing it anyway:
netsh advfirewall firewall add rule name="IISExpress visualstudio app" protocol=tcp localport=12345 dir=in action=allow
Solution 5
Since I am unable to add a comment to @Garret Fogerlie's post and in response to the commenters' issue (@Y.Ecarri and @SamuelEdwinWard), I followed what Garret suggested, using Visual Studio 2013, running it in Admin mode and changing the application.config
file.
After launching debug and seeing that I got the same error message, I went back into application.config
and saw that a new entry for my site had been created just like Y.Ecarri's issue.
So I stopped debugging, kept my solution open in Visual Studio, and edited the application.config
file again for the new entry. I also simply removed the *
sings and localhost
entirely, so I had the following for the new entry:
<binding protocol="https" bindingInformation=":44300:" />
gator88
Updated on July 08, 2022Comments
-
gator88 almost 2 years
I have a test ASP.NET MVC3 application developed in VS2012. When I start debugging the app is accessed from the host machine via the request to
http://localhost:<portnumber>
. But if I try to access the same application from the remote machine in the intranet via thehttp://<ip>:<portnumber>
I getHTTP error 400: Bad request. Invalid Host Name.
As far as it runs on IIS Express any server configuration is inaccessible.Are there any ways of solving this?