Umbraco CMS 401 Error With .NET SDK 10.0.100-preview.7

by Luna Greco 55 views

Hey everyone,

We've got a tricky issue to dive into today: a 401 error when loading resources in Umbraco CMS while running .NET SDK 10.0.100-preview.7.25380.108. This can be a real headache, especially when you're trying to get your Umbraco site up and running smoothly. Let's break down the problem, explore the steps to reproduce it, and figure out what might be going on.

The Issue: 401 Unauthorized Error

The core of the problem is a Failed to load resource: the server responded with a status of 401 () error in the browser console. This error means that the server is refusing to provide the requested resource because the client (your browser) hasn't provided the correct authentication credentials. In simpler terms, it's like trying to enter a members-only club without a valid membership card. The server is saying, "Sorry, you're not authorized to access this."

Why This is Happening

A 401 error typically arises when the server requires authentication, but the client either hasn't sent any credentials or the credentials sent were invalid. This can be due to a variety of reasons, including:

  • Incorrect Configuration: Misconfigured authentication settings in Umbraco or the underlying .NET application.
  • Missing Authentication Headers: The browser might not be sending the necessary authentication headers with the request.
  • Session Issues: Session cookies or other session-related data might be missing or corrupted.
  • .NET SDK Bug: In this specific case, the issue seems to be related to a particular version of the .NET SDK (10.0.100-preview.7.25380.108), suggesting a potential bug or compatibility problem.

Is there an existing issue for this?

  • [x] I have searched the existing issues

Describe the bug

When running against 3rd part application with dotnet-sdk-10.0.100-preview.7.25380.108, UmbracoCMS app failed load page with below error:

chrome-error://chromewebdata/:1 Failed to load resource: the server responded with a status of 401()

Application Name: UmbracoCMS

OS： Windows 11 24H2

CPU: X64

.NET Build Number: dotnet-sdk-10.0.100-preview.7.25380.108

App & App Source checking at: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/2541067

Github Link: https://github.com/umbraco/Umbraco-CMS

Verify Scenarios:

  1. Windows 10 21H2 AMD64 + dotnet-sdk-9.0.303: Pass
  2. Windows 10 21H2 AMD64 + dotnet-sdk-10.0.100-preview.7.25374.104: Pass
  3. Windows 10 21H2 AMD64 + dotnet-sdk-10.0.100-preview.7.25380.108: Fail

Expected Behavior

The login page should load successfully. This is the first step in accessing the Umbraco CMS, and a 401 error here prevents users from even getting to the login screen. A smooth login experience is crucial for any CMS, as it's the gateway to managing your website's content and settings. When the login page fails to load, it not only blocks access but also creates a frustrating experience for users.

Steps to Reproduce the 401 Error in Umbraco CMS

To really get to grips with this 401 error, let's walk through the steps to reproduce it. This will help you confirm if you're facing the same issue and provide a solid foundation for troubleshooting. The key here is to follow the steps meticulously, ensuring each configuration is correctly set. By recreating the error, you'll gain a better understanding of the environment in which it occurs, which is crucial for identifying the root cause.

App Repro Steps

These steps outline how to reproduce the issue with a pre-built application.

  1. Ensure the Correct .NET SDK is Installed:

    • The machine must have dotnet-sdk-10.0.100-preview.7.25380.108 installed. This specific SDK version is implicated in the bug, so it's crucial to use this version for reproduction. Using a different version might not trigger the error, leading to inaccurate results.

  2. Copy the Application Files:

    • Copy [\...\]2541067\Umbraco-CMS to your local machine. This step involves transferring the necessary application files to your local environment, which is essential for running and testing the application in isolation. Make sure the copy process is complete and no files are corrupted during the transfer.

  3. Update the Runtime Configuration:

    • Update Umbraco.Web.UI.runtimeconfig.json with the correct .NET SDK runtime version:
    "frameworks": [
      {
        "name": "Microsoft.NETCore.App",
        "version": "10.0.0-preview.7.25380.108"
      },
      {
        "name": "Microsoft.AspNetCore.App",
        "version": "10.0.0-preview.7.25380.108"
      }
    ],
    • This step is critical because it configures the application to use the problematic .NET SDK version. The runtimeconfig.json file specifies the runtime dependencies for the application. By setting the version attribute to 10.0.0-preview.7.25380.108 for both Microsoft.NETCore.App and Microsoft.AspNetCore.App, you ensure that the application targets the correct runtime environment.

  4. Launch the Application:

    • Launch Umbraco.Web.UI.exe. This is the executable file that starts the Umbraco CMS application. Running this file will initiate the application, and if the configuration and environment are set up correctly, it should lead to the error.

  5. Open Umbraco in the Browser:

    • Click the "Open Umbraco" button. This action attempts to open the Umbraco CMS in your default web browser. If the 401 error is present, the login page will fail to load, and you'll see the error in the browser's developer console.

App Debug Steps

These steps are more involved and require you to debug the application using Visual Studio. This approach allows for a deeper investigation into the cause of the error, as you can step through the code and inspect variables.

  1. Ensure the Correct .NET SDK is Installed:

    • The machine has dotnet-sdk-10.0.100-preview.7.25372.102 installed. (Note: This step mentions a slightly different SDK version compared to the App Repro Steps. It's crucial to be aware of this discrepancy and potentially test with both versions to understand the full scope of the issue.)

  2. Obtain the Application Source Code:

    • Copy \...\]2541067\AppSourceCode\Umbraco-CMS-contrib.zip and extract it to your local machine, or clone it from https://github.com/umbraco/Umbraco-CMS. This step involves getting the source code of the Umbraco CMS application, which is necessary for debugging and making code-level changes. Cloning from GitHub ensures you have the latest version, while extracting from the provided ZIP file allows you to work with a specific version.

  3. Configure Build Settings:

    • Update `` to false in \Umbraco-CMS-contrib\Umbraco-CMS-contrib\Directory.Build.props file. This step disables treating warnings as errors during the build process. By setting this to false, you prevent the build from failing due to warnings, which can be helpful when debugging and experimenting with the code.

  4. Specify the .NET Version:

    • Update the global.json file to use the .NET version installed on your machine. The global.json file specifies the .NET SDK version to be used for building the application. Ensuring this matches the installed SDK version is crucial for a successful build.

  5. Initialize Git Repository:

    • Navigate to \Umbraco-CMS-contrib\Umbraco-CMS-contrib folder and execute the following commands:
    git init
git add .
git commit -m "initial"
    • These commands initialize a Git repository in the project directory. This is often done to track changes and manage versions of the code. While not strictly necessary for reproducing the error, it's a good practice for development and debugging.

  6. Open the Solution in Visual Studio:

    • Open umbraco.sln with Visual Studio. The .sln file is the solution file for the Umbraco CMS project. Opening it in Visual Studio loads the entire project, allowing you to build, debug, and run the application.

  7. Build the Project:

    • Build \Umbraco-CMS-contrib\Umbraco-CMS-contrib\src\Umbraco.Web.UI\Umbraco.Web.UI.csproj project. Building the project compiles the source code into executable files. This step is necessary before you can run the application in debug mode.

  8. Update Runtime Configuration (Again):

    • Update \Umbraco-CMS-contrib\Umbraco-CMS-contrib\src\Umbraco.Web.UI\bin\Debug\net9.0\Umbraco.Web.UI.runtimeconfig.json file with dotnet-sdk-10.0.100-preview.7.25380.108 runtime version:
    "frameworks": [
      {
        "name": "Microsoft.NETCore.App",
        "version": "10.0.0-preview.7.25380.108"
      },
      {
        "name": "Microsoft.AspNetCore.App",
        "version": "10.0.0-preview.7.25380.108"
      }
    ],
    • This step, similar to the one in the App Repro Steps, configures the application to use the specific .NET SDK version. It's crucial to ensure the runtime configuration is correct for the debugging environment.

  9. Configure Launch Settings:

    • Switch to launch application with Umbraco.Web.UI from Visual Studio. This step configures Visual Studio to launch the Umbraco.Web.UI project when debugging. It involves selecting the correct launch profile in the Visual Studio settings.

  10. Run the Application in Debug Mode:

    • Press F5 to run Umbraco.Web.UI project. Pressing F5 starts the application in debug mode, allowing you to set breakpoints, step through the code, and inspect variables.

  11. First-Time Setup (If Applicable):

    • If it is the first time launching the application, execute the steps from 10~13:

      1. Fill Name, Email, and Password.
      2. Click Next button.
      3. Click Next button.
      4. Click Install button.
      • These steps are part of the initial setup process for Umbraco CMS. If you're running the application for the first time, you'll need to provide the necessary information to configure the CMS.

  12. Subsequent Launches:

    • If it is not the first time launching the application, execute step 14 directly:

      1. Click "Open Umbraco" button.
      • For subsequent launches, you can skip the setup process and directly access the Umbraco CMS.

By following these steps, you should be able to reproduce the 401 error and start debugging the issue. The key is to pay close attention to the configuration and ensure each step is performed correctly.

Exceptions and Error Messages

As mentioned earlier, the main symptom of this issue is the **