Search code examples
.netazureepiserver

Is it normal to get a Gateway Timeout after deploying a new release to Azure?


I have an Episerver website developed in .NET. The web app is hosted as an Azure Web App.

The application works well, but every time I deploy from Dev environment to Staging (pre-production), and/or to Production, I get a Gateway Timeout for about 4 minutes.

I'd just like to know if this is normal, or I'm doing something wrong?


Solution

  • If you swap an application into production, please ensure the staging slot is warmed up before being swapped into production. This eliminates downtime when you deploy your web app. After the swap, the traffic redirection is seamless. If you encounter gateway timeout, I would suggest you use dig web interface to look further into this issue.