> 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/rdm/knowledge-base/troubleshooting-articles/aggregateexception-one-or-more-errors-occurred.md).

# AggregateException - one or more errors occurred

Fix the AggregateException login error when connecting to Devolutions Cloud by adjusting proxy, sign-in, and certificate security settings.

During a connection to Devolutions Cloud, Remote Desktop Manager returns an error beginning with the following text:

```
AggregateException - One or more errors occurred.
at Devolutions.RemoteDesktopManager.RDMOProxy.RDMOWebApiClient.Login(String datasourceID, Boolean forcePromptLucid, String source)
```

Depending on the exact cause of the error, several options can solve this issue.

### Solution 1

1. Go to ***File – Settings – Application – Proxy (Web) – Proxy Settings***.
2. If you do not have a custom Proxy configured, try the ***System Default*** option. If that does not work, try again with ***No Proxy***.
3. If you are in a team environment, we recommend consulting your Administrator to know if you should be using a specific Custom proxy.

### Solution 2

1. Go to ***File – Devolutions Account***.
2. Uncheck the ***Automatic sign-in at startup*** option.

### Solution 3

1. Go to ***File – Settings – Security*** and scroll to the bottom of the page.
2. Under ***Certificate Security***, enable ***Ignore application certificate errors*** and disable ***Check for server certificate revocation***.


---

# 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/rdm/knowledge-base/troubleshooting-articles/aggregateexception-one-or-more-errors-occurred.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.