Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
I am trying to create a custom 500 error page to capture something like:
I have set up the webconfig to match:
<customErrors mode="RemoteOnly" redirectMode="ResponseRewrite" defaultRedirect="~/500.aspx">
But it doesnt seem to capture this url Internal error,
You could try
<customErrors defaultRedirect="500.aspx" mode="RemoteOnly">
Note that by setting the mode flag to RemoteOnly you'll not get to see the 500 page on your local/develop environment.
<httpErrors existingResponse="PassThrough" />
No - this hasn't worked.
One thing that may help - the site is hosted on Azure - do you think there maybe something overriding this?
Could be but unfortunately I don't really have that much experience with umbraco sites hosted on Azure. Few things I could think of not Azure related:
You could also try using the httperrors elements.
ExecuteURL serves dynamic content such as an .aspx page (the path value has to be a server relative URL):
<httpErrors errorMode="Custom" existingResponse="Auto" defaultResponseMode="ExecuteURL" >
<error statusCode="500" responseMode="ExecuteURL" path="/500.aspx" />
File serves a custom error file, such as a .html page:
<httpErrors errorMode="Custom" existingResponse="Auto" defaultResponseMode="File" >
<error statusCode="500" path="500.html" />
Would it be possible to use an Umbraco Content for the 500 error message as well? just like for 404 error.
You can make 500 pages which pull from Umbraco but I would not advise it.
If there is an error in your application then trying to pull content from Umbraco or do anything dynamic may fail also. I've had a situation previously where the 500 page itself was erroring which caused a loop!
We always tend to do static 500 pages for this reason.
Hi. This is what I use and it works on Azure:
There are two places you need to configure in web.config. The first is in system.webServer...
<remove statusCode="500" subStatusCode="-1" />
<error statusCode="500" path="500.aspx" responseMode="ExecuteURL" />
and then in System.Web ...
<customErrors mode="RemoteOnly" defaultRedirect="~/500.aspx" redirectMode="ResponseRewrite" />
As mentioned, for testing locally change mode from RemoteOnly to Off.
Are you getting a default IIS 500 page instead of your custom one?
If so, what is trySkipIisCustomErrors set to in your umbracoSettings.config?
If this is set to false then this may be your issue
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted