ASP.NET Core 502.3 - Bad Gateway

By default, the ASP.NET Core request time out is 2 minutes, and we can change it via request timeout in the setting file. For more ASP.NET Core configuration, you can refer to the ASP.NET Core Module configuration reference

 

   <aspNetCore processPath="dotnet" arguments=".\MyApp.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" requestTimeout="00:20:00">
      </aspNetCore>


Note: For apps running on .NET Core 2.2 or later, the ASP.NET Core Module supports an in-process hosting model. The request timeout attribute doesn't apply to in-process hosting.

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

SQL server- network related or instance-specific error happened while connection establishing

  Instance-specific or network related error happening while connecting to SQL server   Please...

OleDB connection string examples

OleDB connection string examples MS Access (Jet) "PROVIDER=Microsoft.Jet.OLEDB.4.0;DATA...

Do you allow custom COM components?

Do you allow custom COM components? We are not offering to install the custom COM components...

Error when accessing a WCF services

Error when accessing a WCF services Error when accessing a WCF service: "IIS specified...

How to cache static contents to client with UseMaxAge?

You can consider to caches static contents to the client with UseMaxAge if your website has too...

Powered by WHMCompleteSolution