fix(launchSettings): set sslPort to valid port for IIS Express #100
+9
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've run into this issue several times on other ASP.NET Core projects.
Maybe an earlier version of the SDK scaffolded a project with the
launchSettings.json
using an invalid port for IIS Express?In any case, according to dotnet/aspnetcore#2308 this must be true for HTTPS to work with IIS Express
The
sslPort
was set to5001
which causes binding to fail when running the site behind IIS Express and debugging out of Visual Studio.I changed it to
44333
and now you can press the green play button in VS for theIIS Express
profile and everything launches and runs correctly.