> 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/knowledge-base-articles/entry-settings/proxmox-dashboard.md).

# Proxmox dashboard

Configure Proxmox dashboard entries in Remote Desktop Manager, including the server host, certificate errors, ticket or token authentication, and realm.

This article details the many settings and options available for ***Proxmox dashboard*** session entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located. Click the browse button to select a folder, or click the add (<em><strong>+</strong></em>) button to create a new one.</td></tr><tr><td><strong>Display</strong></td><td>How the entry opens: <em><strong>Embedded (tabbed)</strong></em> or <em><strong>Undocked</strong></em>. On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list. When the credentials do not come from the entry itself, the <em><strong>Username</strong></em> and <em><strong>Password</strong></em> of the <em><strong>General</strong></em> tab are disabled.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Host</strong></td><td>The URL of the Proxmox server, for example <code>https://myproxmoxserver.com:8006</code>. Required.</td></tr><tr><td><strong>Ignore certificate errors</strong></td><td>Connect to the Proxmox server even when its certificate cannot be validated.</td></tr><tr><td><strong>Authentication mode</strong></td><td><p>How Remote Desktop Manager authenticates to the Proxmox server:</p><ul><li><strong>Ticket</strong> — Authenticate with a username and password.</li><li><strong>Token</strong> — Authenticate with an API token, identified by its <em><strong>Token id</strong></em> and <em><strong>Secret token</strong></em>.</li></ul></td></tr><tr><td><strong>Realm</strong></td><td>The authentication realm of the Proxmox server. The list is retrieved from the server entered in <em><strong>Host</strong></em> when the entry is opened. Click the <em><strong>Refresh</strong></em> button to retrieve it again. Required.</td></tr><tr><td><strong>Username</strong></td><td>The username used to authenticate. Hidden when <em><strong>Authentication mode</strong></em> is set to <em><strong>Ticket</strong></em> and the selected realm uses single sign-on. Required when visible, unless the credentials come from another entry.</td></tr><tr><td><strong>Password</strong></td><td>The password used to authenticate. Visible only when <em><strong>Authentication mode</strong></em> is set to <em><strong>Ticket</strong></em> and the selected realm does not use single sign-on. Required when visible, unless the credentials come from another entry.</td></tr><tr><td><strong>Token id</strong></td><td>The identifier of the API token. Visible only when <em><strong>Authentication mode</strong></em> is set to <em><strong>Token</strong></em>. Required in that mode.</td></tr><tr><td><strong>Secret token</strong></td><td>The secret value of the API token. Visible only when <em><strong>Authentication mode</strong></em> is set to <em><strong>Token</strong></em>. Required in that mode.</td></tr></tbody></table>

### See also

* [Proxmox dashboard entry](https://docs.devolutions.net/rdm/integrations/virtualization-cloud/proxmox.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://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/proxmox-dashboard.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.
