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

azure app services the page cannot be displayed because an internal server error has occurred.
the webpage cannot be displayed due to an internal server error mbam
500 - internal server error. iis
page cannot be displayed iis
the page cannot be displayed because an internal server error has occurred auth login/aad/callback
passwordstate internal server error
iis redirect 500 internal server error
500 internal server error iis web config

I've installed website on my local machine using IIS 7 successfully. But when I've deployed it on live server, I got the following error:

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

Using the same IIS 7 on live and also set to have Detailed errors in Error Pages module, but still getting the same. What can be a reason?

Thanks

I just got this error and it was caused by a duplicate static content MIME type in the web.config

This error was being returned only on static files - eg images, css, js files were all saying this error (text by itself, no other html or text in the response).

The way to debug this is to look in web config under static content. Here we have a json file extension loaded. This was required on IIS7 but will kill the app if used on IIS8 because json is now pre-loaded at the server level.

    <staticContent>
        <clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="30.00:00:00" />
        <mimeMap fileExtension=".json" mimeType="application/json" />
    </staticContent>

So solution is to remove any of these mimeType entries one at a time to confirm which are needed and which kill your app!

Site Showing "The page cannot be displayed because an internal , Site Showing "The page cannot be displayed because an internal server error has occurred." after adding as virtual application. In Azure App  For performance reasons, in the event that Internet Explorer cannot establish a connection to a proxy server, that proxy server is added to a list of bad proxy servers so that it is not reused for a period of time.

I think the best first approach is to make sure to turn on detailed error messages via your web.config file, like this:

<configuration>
    <system.webServer>
        <httpErrors errorMode="Detailed"></httpErrors>
    </system.webServer>
</configuration>

After doing this, you should get a more detailed error message from the server.

In my particular case, the more detailed error pointed out that my <defaultDocument> section of the web.config file was not allowed at the folder level where I'd placed my web.config. It said "This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false". "

"The page cannot be displayed because an internal server error has , "The page cannot be displayed because an internal server error has occurred." when adding web.configRSS. 15 replies. Last post Sep 20, 2017  Try a simple test to see if your IIS is serving any content at all, or if it is just an application issue. Create a basic HTML document with notepad and upload to your site.

Modify your web.config to display the server error details:

<system.web>
  <customErrors mode="Off" />
</system.web>

You may also need to remove/comment out the follow httpErrors section

  <system.webServer>
    <httpErrors errorMode="Custom">
      <remove statusCode="404" />
      <error statusCode="404" path="/Error/Error404" responseMode="ExecuteURL" />
      <remove statusCode="500" />
      <error statusCode="500" path="/Error/Error500" responseMode="ExecuteURL" />
      <remove statusCode="403" />
      <error statusCode="403" path="/Error/Error403" responseMode="ExecuteURL" />
    </httpErrors>
  </system.webServer>

From my experience if you directly have a server error, this may be caused from an assembly version mismatch.

Check what is declared in the web.config and the actual ddl in the bin folder's project.

the page cannot be displayed because an internal server error has , When a error is 500, that means it's an internal error, meaning internal to the service - the service threw an exception that was not caught. You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »

I've fixed it. I had the following section in web.config :

httpErrors existingResponse="PassThrough"

When I remove it, I got a real error

The Site is not loading Error, Im not sure what happened but all of a sudden the error The page cannot be displayed because an internal server error has occurred. My current set up is both the IIS and DB servers are one and the same. If I uninstall the PasswordState software from the server, remove the IIS site, and reinstall it allowing it to recreate the IIS site itself, will it still be able to re-connect to the DB server (since the name of the server won't be changing)?

In my case, setting httpErrors and the like in Web.config did not help to identify the issue.

Instead I did:

  1. Activate "Failed Request Tracing" for the website with the error.
  2. Configured a trace for HTTP errors 350-999 (just in case), although I suspected 500.
  3. Called the erroneous URL again.
  4. Watched in the log folder ("%SystemDrive%\inetpub\logs\FailedReqLogFiles" in my case).
  5. Opened one of the XML files in Internet Explorer.

I then saw an entry with a detailed exception information. In my case it was

\?\C:\Websites\example.com\www\web.config ( 592) :Cannot add duplicate collection entry of type 'mimeMap' with unique key attribute 'fileExtension' set to '.json'

I now was able to resolve it and fix the error. After that I deactivated "Failed Request Tracing" again.

500 - Internal Server Error for ASP.NET Application, At the end it says — "The page cannot be displayed because an internal server error has occurred." What does it mean? Then I went to the IIS in the server and  An "Internal Server Error" happens within the web server attempting to show you an HTML page. It's typically a server-side problem out of your control.

The page cannot be displayed because an internal server error has occured. Tea Commerce support. Sometimes, when we want to go to the  This problem occurs because the server that is running IIS 7.0 cannot access the configured root directory of the requested location. Make sure that the server that is running IIS 7.0 can access the configured root directory of the requested location.

The page cannot be displayed because an internal server error has occurred. Thread starter VietMinsk; Start date Apr 17, 2014. Tonight I had some problems with an old .NET 2.0 site that I wanted to move from my old host to Azure Website. I did not want to change anything on the site, I just wanted it to run on Azure.

The page cannot be displayed because an internal server error. How can I error occurred while establishing a connection to SQL Server. When attempting to upload a file to a OA2 file space, things don't work out. I'm not sure where to approach this problem. Currently, I'm running OA2 (7x-2.44) on a Windows/IIS 7.0 platform, with MySQL 5.1.72. Most everything about the install went flawlessly - even though I did have to repeat it a couple times over a couple snags. But my OA2 install seems to be mostly doing well. But I do have

Comments
  • It also applies to types such as .woff.
  • I was sure this one didn't apply to me, but I removed everything in staticContent and I can finally see the real error message! Thanks.
  • Clearing the entry before setting it should prevent clashes <remove fileExtension=".json" /> <mimeMap fileExtension=".json" mimeType="application/json" />
  • This is exactly the issue i had... Removing as above did the trick, thanks!
  • this helped me identify the issue
  • In my case, I was migrating a web site from II7 to an IIS8.x Win 2012 Server, and it seems the format for httpErrors may be slightly different between the two servers. Commenting out the httpErrors section fixed the issue for me. I recreated the custom errors from the IIS8.5 GUI after deleting the httpErrors section from the web.config that came from the IIS7.x server.
  • In this case, I believe you could simply install that framework version (or maybe a higher one) from Windows "Programs and Features", under the IIS section.