Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Page Not Found page does not work after installing Umbraco #13247

Closed
nikolajlauridsen opened this issue Oct 20, 2022 · 4 comments · Fixed by #13551
Closed

Page Not Found page does not work after installing Umbraco #13247

nikolajlauridsen opened this issue Oct 20, 2022 · 4 comments · Fixed by #13551

Comments

@nikolajlauridsen
Copy link
Contributor

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

10.3.0/11.0.0-rc1

Bug summary

The 404 page does not work after installing Umbraco until you restart the site.

Specifics

After you've just installed Umbraco you won't get redirected to the default 404 page if you try to go to a page that does not exist, instead, you get an ERR_TOO_MANY_REDIRECTS this does, however, go away and everything works as intended after you reboot the site, so in the grand scheme of things it's not too big an issue.

image

Interestingly the "No Nodes Found" page still works, so to see the error you have to publish a piece of content, otherwise, you'll just get redirected to the "No Nodes Found" page.

Steps to reproduce

  1. Run a fresh site and install Umbraco but DON'T restart the site
  2. Create any piece of routed content
  3. Try to go to a page that does not exist

Expected result / actual result

Expected result: A 404 page should be shown

Actual result: an ERR_TOO_MANY_REDIRECTS occurs

@bergmania
Copy link
Member

Wonder if this is because the installer still kicks in somehow

@nikolajlauridsen
Copy link
Contributor Author

Yeah, I'm suspecting it might have something to do with our catch all fallback route we use when installing

@nikolajlauridsen
Copy link
Contributor Author

Possibly related to #13309 which is marked as sprint candidate, so I'll hold off doing too much with this one

@nikolajlauridsen
Copy link
Contributor Author

Fixed in #13551

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants