Open Closed

504 Gateway Timeout when deployed to IIS #5390


User avatar
0
jason@dripjobs.com created

It doesn't seem to matter whether I create an tiered application or single layer. When deployed to IIS all that happens is a 504 Gateway Timeout. I've deployed a single layer MVC application. 504 Gateway Timeout I've deployed an auth server from the tiered template. 504 Gateway Timeout

I've verified that a regular .Net 7 application works perfectly fine when deployed to the same site in IIS.

I've also successfully run the application locally, pointed to the same database instance and have no problems there.

There must be something that I'm missing, for a release/production deployment to IIS. Deployment guides would go a long way toward eliminating a lot of guesswork when it comes to getting the different templates deployed.

  • ABP Framework version: v7.2.3
  • UI type: MVC
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): BOTH

3 Answer(s)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi

    Can you share the logs? liming.ma@volosoft.com

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi

    Please change the log level to Debug and resend the logs. Thanks.

        public async static Task<int> Main(string[] args)
        {
            Log.Logger = new LoggerConfiguration()
                .MinimumLevel.Debug()
                .MinimumLevel.Override("Microsoft", LogEventLevel.Information)
                .MinimumLevel.Override("Microsoft.EntityFrameworkCore", LogEventLevel.Warning)
                .Enrich.FromLogContext()
                .WriteTo.Async(c => c.File("Logs/logs.txt"))
                .WriteTo.Async(c => c.Console())
                .CreateLogger();
    
  • User Avatar
    0
    jason@dripjobs.com created

    Thank you so much! Once I changed this to Debug I was able to track down the issue.

Made with ❤️ on ABP v9.1.0-preview. Updated on December 05, 2024, 12:19