Page Not Found after upgrading from 16.1.1 to 17.1.0

Hi everyone,

I recently upgraded my project from Umbraco 16.1.1 to 17.1.0. After the upgrade, when I try to visit the site, I only see the following message:

Page Not Found
Cannot render the page at URL '/'.

The same thing happens with all the pages I try to visit on the site.

I have imported uSync and restarted the project, but the pages still don’t show up even though they are published.

Has anyone experienced something similar after upgrading, or does anyone have suggestions on what might be going wrong?

Thanks in advance!

Sounds like you have these lines in your csproj file, you need to remove them:

<RazorCompileOnBuild>false</RazorCompileOnBuild>
<RazorCompileOnPublish>false</RazorCompileOnPublish>

More about this in the docs:

2 Likes

Thank you Søren, I removed them but unfortunately it didn’t solve my problem. I still get Page Not Found. Have you heard about this issue before? I upgraded another project just after the release of 17 and I have the same issue there.

I keep getting these warnings about Umbraco not finding the correct template when entering a specific page, but from what I can see all templates are there.

I get the same error about templates in my other project which I upgraded to 17

I read some other threads here at the Forum where several people gave me the advice to install Umbraco.Cms.DevelopmentMode.Backofficeand so I did. It now works and I can reach all the pages, but will this also work in production when I deploy the upgrade of Umbraco 17? Or is this package just solving my issue when I’m working locally in development environment?

This will work in production, as there the Razor views will be compiled on publish, which was a thing that didn’t happen on your local machine before.

The alternative to the package is to switch models mode to SourceCodeAuto or SourceCodeManual and then re-generate the models in Settings → Models builder, by the way.

1 Like

Umbraco.Cms.DevelopmentMode.Backoffice package solved the problem, thank you Jacob

1 Like

Having similar issues on 16.4