Umbraco:CMS:Runtime:Mode Production crashes Umbraco cloud

Questions
,
1

Hi

Reading this post: Runtime Modes | Umbraco CMS I’ve changed appsettings.Production.json to this

"Umbraco": {
  "CMS": {
    "Runtime": {
      "Mode": "Production"
    },
    "Hosting": {
      "Debug": false
    },
    "Global": {
      "UseHttps": true
    },
    "WebRouting": {
      "UmbracoApplicationUrl": "https://www.site.se/"
    },
    "ModelsBuilder": {
      "ModelsMode": "None"
    }
  }
}

But the site crashed with a 500-error and I get no information in the logs. I’ve tried this setup on my local machine as well to try it out and get a 500 error there too (with no specific logs neither in IIS-logs or umbraco logs).

2

Can you run it locally in kestrel, like using dotnet run? Usually that will tell you. There are some nuances in the required settings that are not always in the docs.

3

500 errors on Cloud can be seen in Kudu (for the environment where it’s crashing) > Debug console > Logfiles > eventlog.xml

The newest events are at the bottom of that file.

image
image1068×577 66.7 KB

As Luuk notes, you could run it locally, setting ASPNETCORE_ENVIRONMENT=Production - I usually just add something to my launchSettings.json, for example:

    "Kestrel [ENV: Production]": {
      "commandName": "Project",
      "dotnetRunMessages": true,
      "launchBrowser": true,
      "applicationUrl": "https://localhost:44383;http://localhost:65178",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Production"
      }      
    }

That way I can easily select it from VS / Rider and test what happens before deploying the changes, any errors will show in VS/Rider.

4

Hi Sebastian

Thank you for your snippet. I tried it out, but still only getting 500-errors with no error showing in the output (only a bunch of “(CoreCLR: clrhost): Loaded” rows :S.

Just changing Runtime:Mode to ”Develop” (but keeping every other setting) makes the site start again.

5

I actually just get a white screen on local, so that didn’t work :sweat_smile:

Anyway, did you check your eventlog.xml? Should be some info in there. Also, can you post your actual appsettings.Production.json (redact any secrets etc). Often it’s just a case of putting something in the wrong place.

6

2 suggestions: are you running httpS for your kestrel? Or else you need to create some self-signed-certs (I had the same white-screen-of-NoInfo). Secondly, perhaps you experience sql issues because .net 10 + Umb17 + azuresqledge (tnx Sebastiaan) do not support CLR so in my case I need to change system (no more pi!..).

Greetings from Nijmegen

7

Just to check you’ve also done the other pre-requisite for production mode?

To compile your views at build/publish time, remove the <RazorCompileOnBuild> and <RazorCompileOnPublish> properties from your project file (see the Development mode section). If you don’t, Umbraco can’t find the templates and will return 404 (Page Not Found) errors.

Another one we’ve come across that has hidden 500’s is if you’ve some how ended up with the DataBase umbraco version ahead of your site dll version and a migration plan is in place that can’t be found. (eg DB could be v17 , but dll’s v17 rc4?)

8

Hi Mike

Yes, those I have removed.

In umbracoKeyValue I’ve got this row:

Umbraco.Deploy+UmbracoCmsVersion 17.0.0+da502e0

Which is the same as the dll-version.

image
image332×262 4.72 KB

9

If I am correct your site needs to be built in release mode as well for Production mode.

10

Usually the tracelog will tell you whats wrong.

You can find it in Kudu (site/wwwroot/umbraco/Data/Logs or something like that). Should also be available through the portal.

11

I have a similar issue when using “Production” as runtime mode but in Azure and not Umbraco Cloud.
In my web.config i enabled stdoutLogEnabled=“true” and found out Umbraco could not find my views.

When testing locally this in Release and Production mode the application works.
I have used the same settings recommended in documentation for appsettings and csproj.

12

In production mode, views are precompiled and will not be found on the disk I think. Did you read this part:

Ensure you have the <CopyRazorGenerateFilesToPublishDirectory>true</CopyRazorGenerateFilesToPublishDirectory> property set in your csproj project file, so Razor views are always copied to the publish directory. This is required by the CMS to display the contents in the backoffice, for Forms to lookup custom theme views and for Deploy to be able to compare schemas (otherwise you’ll get schema mismatches).

And also:

You can remove the following properties from your csproj project file to enable the compilation of Razor views (which also ensures your views do not contain compilation errors and is a prerequisite for enabling Production mode):

Copy

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

Thanks for the tip. I could see now that ModelsMode should be “Nothing” and not “None”. Big effing DOH on my part there.

Thank you guys for all your help.

14

Instead of “guys”, may we suggest, for example: “folks", “Umbracians”, “all”, or “everyone”? We use gender inclusive language in this forum :grinning_face: (read more)

15

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.