> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/resources/other-resources/devolutions-login-page-does-not-open-in-the-browser.md).

# Devolutions login page does not open in the browser

Fix the Devolutions login page not opening in your browser by adjusting extension settings or switching to a different browser.

When trying to connect to a Devolutions product such as Devolutions Cloud or Devolutions Server, a connection page should open in your browser to allow you to enter your credentials. This window can sometimes be blocked by your browser or an extension installed on it. In this case, no error message is shown in the Devolutions product since the issue comes from the browser.

#### Solution <a href="#solution" id="solution"></a>

First, change your browser or browser extension settings to remove or disable the setting that blocked the credentials prompt window. Try connecting again.

If that does not work, disable or delete the extension that causes the issue or change browser. Try connecting again.

If you still encouter issues, please [contact our customer support team](mailto:service@devolutions.net).


---

# 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.devolutions.net/resources/other-resources/devolutions-login-page-does-not-open-in-the-browser.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.