> 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/server/knowledge-base/troubleshooting-articles/unable-to-log-into-a-devolutions-server-account.md).

# Unable to log into a Devolutions Server account

Unable to log into a Devolutions Server account and receiving error message ***Invalid username/password*** or ***COMException - The user name or password is incorrect***.

### Solution

With an access to a local Devolutions Server user to connect to the web interface:

1. Go to ***Administration – Server Settings – Authentication – Domain***.
2. Make sure the administration credentials are configured: ***VaultADReader*** in [Pre-Deployment Account Survey](https://docs.devolutions.net/server/kb/knowledge-base/pre-deployment-account-survey/).
3. Once saved, you should be able to connect using AD credentials.

Without an access to a local Devolutions Server user:

1. Download an older version of the Devolutions Server Console.
2. Uninstall the new Devolutions Server Console first (from the control panel) and install.
3. You will be able to click the user button in the top bar to create an account (with admin rights), and then authenticate with that user.


---

# 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:

```
GET https://docs.devolutions.net/server/knowledge-base/troubleshooting-articles/unable-to-log-into-a-devolutions-server-account.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.