How to debug a 503 error on an azure web app?

0
votes

When deployed locally my application works without any problems. I have been fighting with this error for 2 days on the azure deployment now:

Going to a link for my azure web app I get this error :

This page isn’t working
www.mypage.com is currently unable to handle this request.
HTTP ERROR 503

Trying to attach the debugger yields : Unable to find a process called dotnet with arguments .\Unikyte.SPA.dll. The process may still be starting, please try again.

There doesn't appear to be anything useful written in the logs.

In detailed logs I found that every time I try to visit the page a new file is generated and it looks like this :enter image description here

Obviously the dotnet process isn't running, but by default after deployment it should run... Should I manually do dotnet run on my production dll?

1
azureasp.net-core.net-core
You can try enabling stdout logging in web.config via Kudu. And then check out the logs. – juunas

1 Answers

2
votes

There could be many possible reasons for the issue.

Symptom: When you browse to the web app, it returns a HTTP "502 Bad Gateway" error or a HTTP "503 Service Unavailable" error.

Cause: This problem is often caused by application level issues, such as:

  • requests taking a long time
  • application using high memory/CPU
  • application crashing due to an exception.

To troubleshoot further on this, follow the troubleshooting guide which will help you to find out the root cause and fix.

Also, make sure the deployment files are available under Web App using Kudu Console.

To access KUDU console using your deployment credentials, navigate to https://yourappname.scm.azurewebsites.net -> Debug Console-> CMD -> navigate to the wwwroot folder (D:\home\site\wwwroot>).

Hope this helps.