> For the complete documentation index, see [llms.txt](https://docs.portainer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.portainer.io/sts/faqs/troubleshooting/logs-errors-and-debugging/portainer-fails-to-start-with-invalid-url-for-trusted-origin-error.md).

# Portainer fails to start with "invalid url for trusted origin" error

#### Issue

* Portainer fails to start and logs a fatal error such as:

```
  failed to build server | error="invalid url for trusted origin. Please check the trusted origins flag. trusted_origin: \"portainer.example.com\""
```

* After startup, browser requests return `403 Forbidden` on state-changing actions, with `CSRF check failed` entries in the server logs.

#### Cause

As of Portainer version 2.41, CSRF protection has been migrated from `gorilla/csrf` to Go's standard library. This is a breaking change to how trusted origins are validated. Each entry in `PORTAINER_TRUSTED_ORIGINS` must now be a **full URL including scheme** (`http` or `https`). Bare hostnames are no longer accepted. Optionally, a port may also be included.

| Format                               | Valid?             |
| ------------------------------------ | ------------------ |
| `portainer.example.com`              | No longer accepted |
| `https://portainer.example.com`      | Valid              |
| `https://portainer.example.com:9443` | Valid              |

#### Solution

Update all entries in your `PORTAINER_TRUSTED_ORIGINS` configuration (CLI flag or environment variable) to use full URLs with scheme.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.portainer.io/sts/faqs/troubleshooting/logs-errors-and-debugging/portainer-fails-to-start-with-invalid-url-for-trusted-origin-error.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.