Common causes of this issue:
The application process failed to start
The application process started but then stopped
The application process started but failed to listen on the configured port
The application process started but then stopped
The application process started but failed to listen on the configured port
Troubleshooting Options:
Option 1: Enable logging the application process’ stdout messages in web.config
- Create folder "logs" under your site root folder if it does not exist
- Open the root web.config file of your site, set stdoutLogEnabled to true
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="dotnet" arguments=".\Test.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" />
</system.webServer>
</configuration>
You will want to adjust the log level in the appsettings.{environment.}json file in order to capture all log info.
"Logging": {
"LogLevel": {
"Default": "Information",
"Microsoft": "Warning",
"Microsoft.Hosting.Lifetime": "Information"
}
}
Option 2: Enable development mode in web.config
- Please note: after you switch to development mode, your application will read configurations from appsettings.development.json file instead of appsettings.json file.
<configuration>
<system.webServer>
<aspNetCore .....>
<environmentVariables>
<environmentVariable name="ASPNETCORE_ENVIRONMENT" value="Development" />
</environmentVariables>
</aspNetCore>
</system.webServer>
</configuration>