.NET Core 2.2 Publishing problems - asp.net-core

Question

I have a web hosting which supports ASP.NET Core 2.2. I tried to publish my own asp.net core 2.2 project in it and it worked with just design. And then I added Identity in the project and I added the same database in the host (exported and imported db which created with migrations). I changed the database connection as well, but when I'm trying to publish the same project it gives me this error :
HTTP Error 502.5 - Process Failure
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
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
For more information visit: https://go.microsoft.com/fwlink/?LinkID=808681
Here is my connection string :
"ConnectionStrings": {
"IdentityConnection": "Data Source=.\MSSQLSERVER2016;Database=ChatIdentity;Integrated Security=False;User ID=halitkal;Password=*;Connect Timeout=15;Encrypt=False;Packet Size=4096"
},
Here is my webconfig file :
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath="dotnet" arguments=".\ChatSite.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="InProcess" />
</system.webServer>
</location>
</configuration>
<!--ProjectGuid: 028aa0e3-c5ef-4f5c-87ac-e8de39c5ca44-->

Answer 1

Turn on the stdout logs by changing the next line in the web.config
aspNetCore processPath="dotnet" arguments=".\ChatSite.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="InProcess" />
Don't forget create a folder named logs in the same directory that you have your dll files.
Then reboot the application (Application pool if you´re hosting in IIS) then make an http request and then check for generated log, that should give to you the detail about the error.
If that not works, make sure you have the right runtime installed.