1

I have a web app on Azure. Up until a couple of hours ago, it was working perfectly: i could deploy, restart, stop, restart, etc and it would work as expected.

I decided to scale up, changing from S1 Standard to S2 Standard. Now, if I restart my app after I deploy it, or stop and restart, the app seems to enter some kind of a lockdown mode and all requests are blocked with a 403.

One of the detailed error pages says "A default document is not configured for the requested URL, and directory browsing is not enabled on the server.", so I went to IIS manager and disabled default documents. The app seemed to have restarted automatically, and it started working again.

However, after restarting, all requests were denied again!

Anybody has any idea of what could be going on?

goamn
  • 1,939
  • 2
  • 23
  • 39
victor
  • 1,532
  • 1
  • 13
  • 32
  • Have you attempted to redeploy to a new Web App? (I realize that's a Band-Aid, and not the root cause, but just curious if the code base you have can still be deployed as-is, functionally) – David Makogon Sep 06 '17 at 17:43

1 Answers1

0

Anybody has any idea of what could be going on?

so I went to IIS manager and disabled default documents.

I assume that action causes the 403 error. I also can repro it if I disable the default documents with IIS remote manager. Please have a try to enable it. I also find a smilar SO thread.

Update:

We could troubleshoot it with the following ways:

  1. Add a default document in the default document list and republish it again.

  2. Scale service plan down and Scal up to S2.

  3. Create a new serviceplan and move the WebApp to the new serviceplan.

  4. If all of those can't solve the issue, we also could connect to the Azure support team for help.

Community
  • 1
  • 1
Tom Sun - MSFT
  • 24,161
  • 3
  • 30
  • 47
  • It happens even with def docs enabled. Things is that before scaling up I did not have this problem, and I never used def docs. – victor Sep 06 '17 at 07:52
  • We could troubleshoot it with the following ways: 1. Add a default document in the default document list and republish it again. 2. Scale service plan down and Scal up to S2. 3. Create a new serviceplan and move the WebApp to the new serviceplan. 4. If all of those can't resolve the issue, we also could connect to the Azure support team for help. – Tom Sun - MSFT Sep 06 '17 at 08:05
  • 1
    a comment would have been a better option for what you have written. – It's a trap Sep 06 '17 at 09:47
  • @It'satrap Thank you for your suggestion. I have updated the answer. – Tom Sun - MSFT Sep 06 '17 at 10:04
  • If I add an Index.html to the root, then my request returns that page, but I get 404 for all controllers. It is like it is not registering any of my routes. – victor Sep 12 '17 at 04:49
  • Have you try the troubleshoot ways? If all of those way can't solve the issue, we also could connect to the Azure support team for help. – Tom Sun - MSFT Sep 25 '17 at 03:27