We have sitecore CMS (asp.net application) hosted in Azure Web Apps. On web.config the excutiontime has been set to 1 hour and the session and form auth is set to expire in 20minutes.
When I try to install the sitecore update package I keep getting error below within 4 minutes.
<html><head><title>500 - The request timed out.</title></head><body> <font color ="#aa0000"> <h2>500 - The request timed out.</h2></font> The web server failed to respond within the specified time.</body></html>
Appreciate if you could help me understand if there any explicit timeout setting on web app that that overwrite my web.config settings? If yes, how do we increase?
I had a look at few thread posts but didn't help:
Azure Web App or App Service: Service calls(web server) times out after nearly 4mins
How To Prevent HttpWebRequest with long response from timing-out Azure Web App
Thanks.
Related
I have hosted .net core base custom Rest API and hosted at Azure. This is working fine at Local but getting request timeout error after hosting
500 - The request timed out.
The web server failed to respond within the specified time.
Please help
I hosted a Web Api to azure app service. Everything works fine when I published it.
After a couple of days, the Web Api stops responding. But my app service is still running.
Even added application Insight Logs to all the code, to all the catch blocks, even then its not helpful.No exception was logged to date.
Checked the following, but doesn't seem to be helpful.
Thread Count of app service.
CPU time.
and this was the error when I tried to hit from postman after my web API is down.
<html><head><title>500 - The request timed out.</title></head><body> <font color ="#aa0000"><h2>500 - The request timed out.</h2></font> The web server failed to respond within the specified time.</body></html>
When I restarted my app service the web API started working and stops again after a couple of days.
I think your app service is being idled out due to inactivity . Please set always on to be true in the general settings in configuration blade , you can check out link
App service configuration.
I have ASP.NET Core Web API deployed as App Service on Azure. App Service is set up to require Client Certificate. Also AlwaysOn for App Service is set to True.
Issue is that first request with small payload sent to Web API takes approximately 2-3 seconds, and with large payload timed out. But after first small successful request, next one with large payload executes in less than a second. After some period of inactivity the issue occurs again, and first request to Web API again either takes time or timed out.
When Require Incoming Certificate is disabled, no issues with first request execution time, it executes quite fast always.
Web apps are unloaded if they are idle for a set period of time.
Quoted from official docs:
The downside is that the response to the first request after the web app is unloaded is longer, to allow the web app to load and start serving responses.
If you're using a Basic and Standard service plan, you can turn on the Always On setting to keep the app always loaded:
In the Azure portal, go to your web app.
Select Application settings.
For Always On, select On.
I am using an api which takes more time to give response. If I tested the web api that was deployed in IIS from postman, It works without any time out. If I tested the same api that was deployed in azure, It gave me timeout.
Somewhere I read that you need to set the timeout in client application. I used postman in both cases. I verified the timeout for postman. It is infinity.
Can you give me the solution?
I think that you hit the default timeout of Azure Web Apps (i think it is 3 minutes, if i remember correctly). Could you set SCM_COMMAND_IDLE_TIMEOUT from the portal - web app settings => app settings => add the setting with the needed value (to say 360 (in seconds)). Reference.
My App is hosted in Azure Websites and uses SignalR
Azure started a new thing where they shut down the website if it's been idle for more than a few seconds. i.e. no requests.
For some reason, having an active outgoing websockets connection does not seem to keep the website "active". So the WebSockets client starts getting 403 (Site Disabled) until you make another http request.
Has anyone else encountered this issue?
Does anyone have a solution?