> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/cookies/troubleshooting.md).

# Troubleshooting

The most frequent causes of a cookie banner that does not appear, and how to fix them.

If the cookie banner does not appear, check the following points in order.

1. Check the allowed URLs. In the menu, click **Cookie consent** > **Banners**, open the banner, then the **Settings** section. The address of your website must be listed in **Urls authorized (Allowed origins)**, in the format `https://myurl.com`, without a path. This is the most frequent cause: an origin missing from the list is refused.

   <figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-a8ee82c2d82335110e22fef00abf48d0e08eaa5a%2Fcookies-configure-6.png?alt=media" alt="The Settings section with the Urls authorized (Allowed origins) field"><figcaption><p>The "Urls authorized (Allowed origins)" field</p></figcaption></figure>
2. Check the status of the banner. In the editor, the **Status** switch must be **Enabled**.
3. Check the validity of your public API key (do not use the private key). Click the gear icon in the top bar (**Organization settings**), then **Api keys & MCP**. Check that the key exists and has not expired. See [API key management](/en/features/settings/api-keys.md).

   <figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-48cf9361a1c99d0e8d5b2a5fd00bef0405f61be8%2Fcookies-quickstart-1.png?alt=media" alt="The Api keys &#x26; MCP page with the list of keys"><figcaption><p>The "Api keys &#x26; MCP" page</p></figcaption></figure>
4. Check that you did not set a display trigger by mistake. In the **Triggers** section, a **Scroll before trigger in %** value that is too high prevents the banner from appearing when the visitor arrives on the page.
5. Check the options that hide the banner. The **Disable the banner display (all cookies with default consent will be triggered)** option hides the banner, and so does **Enable Global Privacy Control (GPC)** for visitors whose browser sends this signal. A visitor who already made a choice no longer sees the banner: delete the `consent-eu` cookie from your browser to test.
6. Check your subscription. To use the cookie consent banner, your subscription must include the feature. If the **Cookie consent** menu does not appear in the navigation, the feature is probably not included: contact your organization owner. If the subscription has expired, the API refuses the banner configuration. For more information, you can contact the [support](mailto:support@dastra.eu).
7. For any other problem, [contact the support](/en/getting-started/support/request.md).


---

# 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://doc.dastra.eu/en/features/cookies/troubleshooting.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.