How to debug Azure 500 internal server error

My newly deployed site is getting a 500 internal server error. I’m trying to deploy Umbraco to Azure.

I’ve turned off custom errors but that doesn’t help.

Is there anyway to see the error that Azure is throwing?

I was able to edit my configuration and setup RDP into my web role. Once on the box I couldn’t go to it via IP because I’m using the umbraco accelerator. There was a binding in IIS to go to If I used that I could see the page from the server and the error came up.


Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

For 500 errors, one good way is to turn diagnostics on and to look at the logs – both the application event logs and the failed request logs might help. Here’s one post about this –

As Igorek has said, you can also use RDP (remote desktop) to log in and to check the app – here’s a good blog post about this –

My guess is that you might be missing one or more Assemblies from the deployed package

Method 2

You don’t have to use RDP, simply by turning off custom error in Web.Config will do. But make sure you are adding that in the root Web.Config, that will do the trick.

Here is an example of mine:

    <customErrors mode="Off" />
    <compilation debug="true" targetFramework="4.5">

Just be aware that there are multiple web.configs in a typical project.. make sure you are adding this in the root web.config (where your Global.asax is) and NOT in Views folder.

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes
Article Rating
Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x