Home page always redirects to error page - but cannot find any errors
Hi all,
I've had an issue with a client's umbraco intranet site for the past few days and I'm at my wit's end on finding a solution. They're using umbraco 6.1.6
Whenever anyone tries to go to the home page (either with intranet/ or intranet/home) it always redirects to the error.aspx page using error 302.
Problem is, i cannot for the life of me find any errors that are causing it to go to the error page. The logs have no errors being reported, there's nothing in the console either, and even when i turn off everything i can find that would tell it to redirect to the error page, it is still doing this.
The rest of the site can be accessd just fine.
I've tried rolling back the home page content, republishing the entire website, clearing the recycling bin and the web cache, checking the global.asax is the right the version, and even editing the home.master file to comment out parts of it to see if it's something in the file itself. I really don't know what to do anymore, and the lack of any errors has proven to be incredibly frustrating.
Cause of the issue has been found, a section on the page had a bunch of links in it and one of the clients had added something in that was causing the error. Rolling back the page didn't fix it because it doesn't keep track of the links that are added and removed (also for some reason commenting out that part of the page didn't fix the error and i had to temporarily delete it entirely)
May be there a bad link or snippet of code was inserted into the Home page content. This caused Umbraco to trigger a custom error redirect (to error.aspx) even though no clear error showed up in the logs.
So please Edit the Home page and remove (or correct) the broken link/snippet.
Republish the page.
If rolling back content doesn’t help, manually inspect the Rich Text Editor (or macros) to ensure the bad link isn’t still hidden somewhere.
And for the Future Prevention, Temporarily set customErrors to “Off” in Web.config during development. This will help reveal detailed errors instead of just redirecting, making it easier to spot problems early.
Home page always redirects to error page - but cannot find any errors
Hi all,
I've had an issue with a client's umbraco intranet site for the past few days and I'm at my wit's end on finding a solution. They're using umbraco 6.1.6
Whenever anyone tries to go to the home page (either with intranet/ or intranet/home) it always redirects to the error.aspx page using error 302. Problem is, i cannot for the life of me find any errors that are causing it to go to the error page. The logs have no errors being reported, there's nothing in the console either, and even when i turn off everything i can find that would tell it to redirect to the error page, it is still doing this.
The rest of the site can be accessd just fine.
I've tried rolling back the home page content, republishing the entire website, clearing the recycling bin and the web cache, checking the global.asax is the right the version, and even editing the home.master file to comment out parts of it to see if it's something in the file itself. I really don't know what to do anymore, and the lack of any errors has proven to be incredibly frustrating.
Any ideas on what else i could try to fix it?
Thanks all, Abi
Cause of the issue has been found, a section on the page had a bunch of links in it and one of the clients had added something in that was causing the error. Rolling back the page didn't fix it because it doesn't keep track of the links that are added and removed (also for some reason commenting out that part of the page didn't fix the error and i had to temporarily delete it entirely)
May be there a bad link or snippet of code was inserted into the Home page content. This caused Umbraco to trigger a custom error redirect (to error.aspx) even though no clear error showed up in the logs.
So please Edit the Home page and remove (or correct) the broken link/snippet.
Republish the page.
If rolling back content doesn’t help, manually inspect the Rich Text Editor (or macros) to ensure the bad link isn’t still hidden somewhere.
And for the Future Prevention, Temporarily set customErrors to “Off” in Web.config during development. This will help reveal detailed errors instead of just redirecting, making it easier to spot problems early.
is working on a reply...