Sometimes getting timed out connection on Azure app service

Ørjan Olsen 21 Reputation points

I am having an issue with my azure app service sometimes not working over longer periods. When I try to access it through the url in my browser, I am getting connection timed out errors. This happens to all devices on the same network. The service is on a D1 plan. The quotas are not shown as crossed and azure doesn't report any relevant status problems. The weird thing is that if I try to access the site from a different network with a different IP, I can access it. This makes me believe that Microsoft's firewall is blocking me, but I cannot know this for sure. I haven't been doing anything silly and have just been testing my service through what I would consider normal use. Have anybody experienced anything similar or have any idea what the issue could be?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,484 questions
{count} votes

2 answers

Sort by: Most helpful
  1. SnehaAgrawal-MSFT 17,401 Reputation points Microsoft Employee

    Thanks for asking question! Could you please try Enable diagnostic logging for your azure web app to get clear picture on logs what could be causing this issue.

    You may also browse through the Kudu console by accessing the URL: https://<yourwebsite-name>
    Click on debug console for log files.

    Also you may want to know that by default, web apps are unloaded if they are idle for a set period of time. This way, the system can conserve resources. 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.

    In Basic and Standard service plans, you can turn on the Always On setting to keep the app always loaded. This eliminates longer load times after the app is idle. To change the Always On setting:

    1. In the Azure portal, go to your web app.
    2. Select Configuration
    3. Select General settings.
    4. For Always On, select On.

    Let us know if further query or issue remains.

    0 comments No comments

  2. Ørjan Olsen 21 Reputation points

    Hello, thanks for the reply. I have now enabled logging on my service. This issue happens infrequently, but I can peak into the logs next time it happens and come back with more information, should I find something.

    I need to stress that the service is not down as I can access the service from other IP's at the sime time. This also rules out that it could be a cold boot problem.

    As some additional info, the Kudu console does not work either when this problem happens. However, I can access it from a different IP. The problem tends to last for like 2 hours.

    0 comments No comments