Deploying website: 500 – Internal server error

I am trying to deploy an ASP.NET application. I have deployed the site to IIS, but when visiting it with the browser, it shows me this:

Server Error

500 – Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

After fiddling around with the web.config, I got:

The page cannot be displayed because an internal server error has occurred.

How can I see the actual issue behind this server error?


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

First, you need to enable and see detailed errors of your web messages, because this is a general message without giving information on what’s really happening for security reasons.

With the detailed error, you can locate the real issue here.

Also, if you can run the browser on the server, you get details on the error, because the server recognizes that you are local and shows it to you. Or if you can read the log of the server using the Event Viewer, you also see the details of your error.

On IIS 6

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

On IIS 7

        <httpErrors errorMode="Detailed" />
        <asp scriptErrorSentToBrowser="true"/>
        <customErrors mode="Off"/>
        <compilation debug="true"/>

Note: You can avoid the Debug=true. You only need to close the custom errors for a while and get the detailed error page.

Reference: Enabling Windows custom error messaging in Go Daddy’s help articles.

Also, this can help: How to enable the detailed error messages (from IIS).

Method 2

I was pulling my hair out over this issue. Making sure the following entry was in the root web.config file fixed it for me:

    <validation validateIntegratedModeConfiguration="false" />

Remember that you have to add this to the existing XML elements, if they’re already there. You can’t just add at the end of the file, because you can’t have multiple copies of any element.

Method 3

For me, the following code in the web.config was the culprit. When I removed it, the web site worked fine.

    <mimeMap fileExtension=".mp4" mimeType="video/mp4" />

Method 4

I finally solved this “500 Internal server” error when deploying the ASP.NET MVC 3.0 application on godaddy.ocm shared hosting.

somehow there were discrepancies on the version of DLL files referenced and version mentioned in file web.config.

I tried all the options mentioned in various forum. Nothing helped, although everyone suggested the same kind of fix, but somehow it didn’t work in my scenario. Finally after banging my head for two days.
I decided to delete all DLL file reference and delete web.cofig (make a local copy) from the project and let the application throw the error and then add the DLL files one by one making copy to local=true.

After all the DLL files were added, I created a new ASP.NET MVC application and copied the web.config of new application to my actual application.
So my actual application now has a new web.config, and then I copied the connectionstring and other references from the local copy of web.config that I saved.

I just compiled the application and published to a local folder
and FTP the published folder to goDaddy.

It worked and finally my problem was solved.

Method 5

In my case, I put a mistake in my web.config file. The application key somehow was put under the <appSettings> tag. But I wonder why it doesn’t display a configuration error. The error 500 is too generic for investigating the problem.

Method 6

My first attempt to publish and then run a very simple site serving only HTML produced “The page cannot be displayed because an internal server error has occurred.”

The problem: I had the site set to .NET 3.5 in Visual Studio (right click web site project -> Property Pages -> Build), but had the Web Site in Azure configured as .NET 4.0. Oops! I changed it to 3.5 in Azure, and it worked.

Method 7

In addition to the other suggestions, make sure to change the existingResponse attribute of the httpErrors node to Auto from Replace, or to remove that property entirely.

<httpErrors existingResponse="Replace" />
                              ^^^^^^^ not going to work with this here

Method 8

Server Error 500 – Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed. Goddady. Hosting – Web – Economy – Windows Plesk

In my case, I replace this code:

    <httpErrors errorMode="Detailed" /> 
    <asp scriptErrorSentToBrowser="true"/> 
    <customErrors mode="Off"/>
    <compilation debug="true" targetFramework="4.0"/>

Then change framework 3.5 to framework 4. It shows my detailed error. I delete code in:


It solved my problem.

Method 9

IIS also reports status code 500 without any event log hints if there are insufficient permissions on the physical home directory (i.e. IIS_IUSRS has no access).

Method 10

For IIS 10 There is a extra step to do other than changing the customErrors=Off to show the error content.

   <customErrors mode="Off" />
   <httpErrors existingResponse="PassThrough" errorMode="Detailed"/>

Raul answered the question in this link Turn off IIS8 custom errors by Raul

Method 11

Probably your web.config file is wrong or is missing some tag. I solved my problem using the correct config tags for .NET 4.

    <compilation debug="true" strict="false" explicit="true" targetFramework="4.0">
            <add assembly="System.Deployment, Version=, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
            <add assembly="System.Windows.Forms, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
            <add assembly="System.Configuration, Version=, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
            <add assembly="System.Data, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
            <add assembly="System, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
            <add assembly="System.Drawing, Version=, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
            <add assembly="System.Web.Services, Version=, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
            <add assembly="System.Xml, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
            <add assembly="System.Transactions, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID">
            <add namespace="System"/>
            <add namespace="System.Collections"/>
            <add namespace="System.Collections.Specialized"/>
            <add namespace="System.Configuration"/>
            <add namespace="System.Text"/>
            <add namespace="System.Text.RegularExpressions"/>
            <add namespace="System.Web"/>
            <add namespace="System.Web.Caching"/>
            <add namespace="System.Web.SessionState"/>
            <add namespace="System.Web.Security"/>
            <add namespace="System.Web.Profile"/>
            <add namespace="System.Web.UI"/>
            <add namespace="System.Web.UI.WebControls"/>
            <add namespace="System.Web.UI.WebControls.WebParts"/>
            <add namespace="System.Web.UI.HtmlControls"/>
    <authentication mode="None"/>

Method 12

I realized the permissions for the files and folders in your server also matter. I uploaded my files from a linux operating system and usually the permissions are limited for read and write. So when uploaded, the permission are still same as in the local machine.

I had the same error and i just changed the permissions for the folder i had uploaded and the error was gone.

Hope it helps someone.

Method 13

500 Internal Error
Windows Hosting Error

Godaddy Hosting issue

I have been facing the same issue, but now my issue has been resolved. Always use in this hosting this it works.

I will also recommend you all to do whatever changes you are looking to make in your web.config file. Please do it one by one and test the same on the live domain so that you can find the exact problem or the features that your hosting provider does not allow you to use.

<?xml version="1.0"?>

        <trust level="Medium"/>
        <compilation debug="true" targetFramework="4.5">
                <add assembly="System.Data.Linq, Version=, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

        <httpRuntime targetFramework="4.5" />
        <sessionState mode="InProc" cookieless="false" timeout="90" />
        <authentication mode="Forms">
            <forms loginUrl="default.aspx"  
                   name="" />


            <error statusCode="403" redirect="errorpage.aspx"/>
            <error statusCode="404" redirect="errorpage.aspx"/>

        <!--  <httpModules>
                <add name="HTTPCaching" type="HTTPCaching"/>

        <performanceScenario value="HighDensityWebHosting"  />

        <!--  <modules runAllManagedModulesForAllRequests="true">
                <add name="HTTPCaching" type="HTTPCaching"/>

                <clear />
                <add value="default.aspx" />

        <httpErrors errorMode="Detailed" />
        <asp scriptErrorSentToBrowser="true"/>

            <clientCache cacheControlCustom="public"
                         cacheControlMode="UseMaxAge" />

                 <jsonSerialization maxJsonLength="90000000">


Method 14

If you’re using a custom HttpHandler (i.e., implementing IHttpModule), make sure you’re inspecting calls to its Error method.

You could have your handler throw the actual HttpExceptions (which have a useful Message property) during local debugging like this:

    public void Error(object sender, EventArgs e)
        if (!HttpContext.Current.Request.IsLocal)
        var ex = ((HttpApplication)sender).Server.GetLastError();
        if (ex.GetType() == typeof(HttpException))
            throw ex;

Also make sure to inspect the Exception’s InnerException.

Method 15

500 internal server error can arise due to several reasons. First reason might be that web.config file is not properly created, means you have missed some tag in the web.config file. Secondly this error can be due to some code problem. To check which component of the web application is causing this error you can check Application setting in web.config file. The detail of solving and tracing 500 internal server error with diagram is given here:

Method 16

Make sure your account uses IIS 7. For more information, see Customizing IIS Settings on Your Windows Hosting Account.
Follow the instructions in Changing Pipeline Mode on Your Windows IIS 7 Hosting Account. Select Integrated Pipeline Mode.
In your Project References section, set Copy Local to True for the following assemblies:


Add the following assemblies to your project, and then set Copy Local to True:

Publish your application.

Method 17

Sometimes, the reason might be one of your .dll assemblies is not registered correctly on the server.

For example, you can successfully run a C# Excel web application on your local machine with Office installed, while getting the 500 error on server deployment, because there is no Office suite installed on the server, and thus you get the server error.

Method 18

For those who have this possibility (VPS hosting not web hosting):

Connect to your hosting server via Remote Desktop. Open Web Browser from your remote desktop and you will see the detail description of the error.

You don’t need to modify web.config or expose any details to anybody else.

Method 19

If you are using IIS 8.5 it may be that you need to change the ApplicationPool ID setting from ApplicationPoolId to NetworkService

Right click the Application Pool in question, click on “Advanced Settings” and then scroll down to ID – it will probably be set to ApplicationPoolIdentity. Click the button (..) and select NetworkService from the dropdown list instead.

Also make sure that if it is a .NET 2.0 application that you are not referencing the 4.0 framework in your App Pool.

Method 20

Before changing the web.config file, I would check that the .NET Framework version that you are using is exactly (I mean it, 4.5 != 4.5.2) the same compared to your GoDaddy settings (ASP.Net settings in your Plesk panel). That should automatically change your web.config file to the correct framework.

Also notice that for now (January ’16), GoDaddy works with ASP.Net 3.5 and 4.5.2. To use 4.5.2 with Visual Studio it has to be 2012 or newer, and if not 2015, you must download and install the .NET Framework 4.5.2 Developer Package.

If still not working, then yes, your next step should be enabling detailed error reporting so you can debug it.

Method 21

I recently got into same problem, the disk space was full on the server. Clearing some space has resolved the issue.

Method 22

Try compiling in Debug mode (in Visual Studio). If you are in Release mode, a lot of URL Rewrite errors will not be available.

Image shows the Debug selection combobox in Visual Studio

enter image description here

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