43

I have 2 projects, a Web API and a client angularJS project (that was created using the Empty Project template). My client has asked me to force SSL, so for the Web API I created a filterAttribute. Anyway, I changed both projects to be SSL Enabled. The problem is, both projects show their SSL URL to be http://localhost:44300 which obviously won't work.

So I decided to change the applicationhost.config file. For Visual Studio 2015, this appears to be in the .vs folder. When I change it in there, if I open my project it overwrites it and puts it back to 44300.

I tried creating a virtual directory (in the properties of my API) and I tried to override the application root URL. Neither worked.

Does anyone know how I can use a different SSL port?

r3plica
  • 13,017
  • 23
  • 128
  • 290
  • You might download Jexus Manager for IIS Express to make the changes. The file in .vs is not the file to change. – Lex Li Sep 29 '15 at 10:28
  • I will give that a shot – r3plica Sep 29 '15 at 13:26
  • Just in case someone lands here looking for AspNet 5 projects, the regular and SSL ports used by Visual Studio 2015 (Update 1) are hosted, for each project, into the .\Properties\launchSettings.json file. – Ghidello Dec 08 '15 at 15:40
  • "this appears to be in the .vs folder" this comment helped me out thx, I was looking in the wrong folder and therefore the wrong applicationhost.config, was looking in %userprofile%\Documents\IISExpress\config – wallismark Oct 06 '18 at 04:50

4 Answers4

74

I had the same situation with 2 projects. Visual Studio 2015 correctly assigned differing URL port numbers for HTTP but mapped both projects to 44300 for HTTPS.

AFAIK the applicationhost.config in .vs\config seems to define the IIS Express environment and tell IIS Express how to behave when invoked. This information doesn't feedback into Visual Studio.

Visual Studio appears to rely on settings in the .csproj file. This is the SSL port value you see when you look at properties for the project in VS.

I was able untangle the two projects by adjusting both:

  1. Changing the IISExpressSSLPort value in my project's .csproj file
  2. I also needed to ensure that the https binding was included in the applicationhost.config

.csproj

<UseIISExpress>true</UseIISExpress>
<IISExpressSSLPort>44301</IISExpressSSLPort>

applicationhost.config

<bindings>
   <binding protocol="http" bindingInformation="*:58001:localhost" />
   <binding protocol="https" bindingInformation="*:44301:localhost" />
</bindings>

Update:

The file .csproj.user also has SSL Port configuration, to avoid the overwriting of the SSL port number in the applicationhost.config file, .csproj.user should be updated too.

<UseIISExpress>true</UseIISExpress>
<IISExpressSSLPort>44301</IISExpressSSLPort>
Alejandro Tobón
  • 47
  • 1
  • 8
Greg Terrell
  • 1,192
  • 13
  • 17
  • 2
    I found modifying the .csproj file was sufficient. VS appears to rewrite applicationhost.config using my projects current configuration. – CamHart Dec 03 '15 at 22:07
  • I will give this a test because I never found the solution :) – r3plica Dec 09 '15 at 10:44
  • 1
    @Dani, you have to view the file from the File explorer. Visual studio won't show that file by default. – RayLoveless Nov 08 '16 at 20:36
  • 1
    I changed this, but my values in VS are still overwritten with the old portnumber – Marc van Nieuwenhuijzen Jan 04 '17 at 10:57
  • This worked for me, but only HTTP works, not HTTPS. The HTTPS port I'm trying to use is is 8443 but the browser won't connect. In Chrome it says: "This site can’t be reached.The connection was reset." Any ideas? Been struggling with this all day. The HTTP port is 8080. – nmit026 May 05 '17 at 05:03
  • 2
    I believe that the "standard" IIS Express functionality only allows for SSL ports of 44300 to 44399. I have seen posts that describe how to make IIS Express work outside that range, but that wasn't a big deal for me to stay within those 100 addresses. – Greg Terrell May 06 '17 at 11:21
  • worked for me. I have a problem with .csproj.user file. Thank you. – ibrahimozgon Dec 31 '19 at 09:21
  • To @GregTerrell's point, here is the documentation for the custom ports: https://learn.microsoft.com/en-us/iis/extensions/using-iis-express/handling-url-binding-failures-in-iis-express#using-a-custom-ssl-port. I was not able to get it working and is too much setup for us so we are just going to use one of the default ports for now. I wish this range was not necessary. – Hector S. Nov 05 '20 at 20:46
39

For Asp.Net Core see "/Properties/launchSettings.json" file.

Skorunka František
  • 5,102
  • 7
  • 44
  • 69
  • The real MVP! Not sure why the "applicationhost.config" has got an entry, but mine only used the value from "launchSettings.json" – Codendaal Aug 10 '19 at 08:25
  • Had search through the folders to find this. Just do a search across the solution folder for the currently mapped port number to find which file you have to modify to set the new port number. – Jay Jay Jay Oct 10 '19 at 18:43
  • Wow. Just wow. This is the answer we need. Also, if you want to use SSL, don't use it with IISExpress, use "Project" and put the app url to `https://localhost:443;http://localhost:80` – CarComp Jan 20 '21 at 18:57
  • 4
    But if you are using IISExpress, it appears SSL ports must be in the range 44300 to 44399. If you choose something outside this range you will get a "This site can't be reached" or similar blank page. – Fordy Mar 02 '21 at 13:56
3

For vs2015, I found the file applicationhost.config with the correct content under the .vs\ folder in my solution.

Fabricio Martínez Tamayo
  • 63
  • 6
  • 1
    In case anyone else has this isuse, I also found the file there, but changes to it are ignored. If I change the port in the then the next time I hope the project it creates a whole new block and ignores everything I've done. – chrismay Feb 02 '17 at 16:54
0

Right-click on your project, then click on Properties.

Go to the Debug tab then click on Delete.

click on Delete like this image

Adrian Mole
  • 49,934
  • 160
  • 51
  • 83
Hashem Ahmed
  • 71
  • 4