> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/run-in-production/infrastructure-and-ops/health-check/guides/fixedapplicationurl.md).

# Fixed Application URL

Checks that an application URL is available. This URL is used by features that need an absolute URL, such as password-reset and user-invitation emails sent from the backoffice.

The check has three possible outcomes:

| Condition                                                                                             | Result                                                                                                      |
| ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| `UmbracoApplicationUrl` is set                                                                        | **Success**                                                                                                 |
| `UmbracoApplicationUrl` is not set, but `ApplicationUrlDetection` is `FirstRequest` or `EveryRequest` | **Warning** — the application URL is detected from incoming requests. Setting it explicitly is recommended. |
| `UmbracoApplicationUrl` is not set **and** `ApplicationUrlDetection` is `None`                        | **Error** — no URL is configured, and none will ever be detected.                                           |

When the check returns an **Error**, no application URL is available, and nothing will detect one. Features that require an absolute URL - such as password-reset and user-invitation emails - will not work until the configuration is corrected.

## How to fix this health check

There are two ways to resolve this health check. Setting the application URL explicitly is the recommended approach for production environments.

### Option 1: Set the application URL explicitly (recommended)

Provide configuration on the following path: `Umbraco:CMS:WebRouting:UmbracoApplicationUrl`.

This configuration can be set up in a configuration source of your choice. This guide shows how to set it up in one of the JSON file sources.

#### Updating the JSON configuration

The following JSON needs to be merged into one of your JSON sources. By default, the following JSON sources are used: `appSettings.json` and `appSettings.<environment>.json` (`appSettings.Development.json` or `appSettings.Production.json`).

```json
{
    "Umbraco": {
        "CMS": {
            "WebRouting": {
                "UmbracoApplicationUrl": "string"
            }
        }
    }
}
```

One example that can be used in production

```json
{
    "Umbraco": {
        "CMS": {
            "WebRouting": {
                "UmbracoApplicationUrl": "https://www.my-custom-domain.com/"
            }
        }
    }
}
```

{% hint style="info" %}
If the site is hosted on Umbraco Cloud, changing the above configuration will have no effect. The site will always use the URL set in the `umbraco-cloud.json` file, which can not be changed.
{% endhint %}

### Option 2: Enable application URL detection

Alternatively, set `Umbraco:CMS:WebRouting:ApplicationUrlDetection` to `FirstRequest` or `EveryRequest`, so that the application URL is detected automatically from incoming requests. This resolves the **Error** to a **Warning**.

```json
{
    "Umbraco": {
        "CMS": {
            "WebRouting": {
                "ApplicationUrlDetection": "FirstRequest"
            }
        }
    }
}
```

For details on the available detection modes and their security implications, see [Application URL detection](/umbraco-cms/develop-with-umbraco/configuration/webroutingsettings.md#application-url-detection) in the WebRouting settings documentation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-cms/run-in-production/infrastructure-and-ops/health-check/guides/fixedapplicationurl.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.