> 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/how-to-articles/proxmox-dashboard-entry.md).

# Proxmox dashboard entry

Create a Proxmox dashboard entry in Remote Desktop Manager using token or ticket-based authentication to manage and launch Proxmox sessions.

The Proxmox entry in Remote Desktop Manager Windows provides a centralized way to manage and launch Proxmox sessions directly from within your vault.

The dashboard lists the nodes of the cluster on the left. The grid shows the virtual machines (QEMU) and containers (LXC) of the selected node, with their status, ***VM ID***, type, ***IP address***, tags, CPU, memory, storage and ***Uptime***. The ***HA state*** and ***Resource pool*** columns appear when a guest of the node has one. A lock icon in the status column means that Proxmox locked the guest, for example during a backup, a migration or a snapshot, or because it is hibernated; hover over the status to see the reason. A spinner replaces the status while an action runs on the guest.

The server address under the title opens the Proxmox web interface. It appears when the entry uses an `https` address.

### Actions

The toolbar and the context menu of a guest offer ***Start***, ***Shutdown***, ***Reboot***, ***Stop*** and ***Console***, plus ***Reset***, ***Pause***, ***Resume*** and ***Hibernate*** for virtual machines. ***Hibernate*** saves the memory of the virtual machine to disk and stops it; ***Start*** resumes it. ***Stop*** and ***Reset*** ask for a confirmation, since unsaved data in the guest is lost; ***Shutdown*** and ***Reboot*** ask as well. While a shutdown waits on the guest, ***Stop*** can overrule it (Proxmox VE 8.1 and later).

Each action waits for its Proxmox task to end. When Proxmox refuses an action, for example because the guest is locked or the user lacks a permission, or when the task fails, Remote Desktop Manager shows the message of Proxmox. The task also appears in the ***Tasks*** tab.

* ***Copy*** (context menu): copies the name, the IP address or the VM ID of the guest.
* ***Snapshots***: lists the snapshots of the guest, newest first. ***Take snapshot*** creates one, with its memory (***Include RAM***) for a running virtual machine. ***Roll back to snapshot*** restores one, and can start the guest afterwards. ***Delete snapshot*** removes one. Taking a snapshot is unavailable when a disk of the guest is on a storage that does not support snapshots. These actions need the `VM.Snapshot` privilege, or `VM.Snapshot.Rollback` to roll back.
* ***Remove*** (***More*** menu): deletes a stopped guest.

### IP addresses

For a virtual machine, the IP addresses come from the QEMU guest agent: install and start the agent in the guest, and enable ***QEMU Guest Agent*** in the options of the virtual machine in Proxmox. The user or token also needs the `VM.Monitor` privilege on Proxmox VE 8, or `VM.GuestAgent.Audit` on Proxmox VE 9. For a container, the `VM.Audit` privilege is enough. Without them, the ***IP address*** column stays empty; no error is shown. Addresses are refreshed about once a minute for the running guests of the selected node, and at once for the selected guest.

### Details tab

The ***Details*** tab of the bottom panel shows the selected guest: its general information, hardware (processors, memory, disks, network adapters and CD-ROM drives), its notes, and its CPU, memory and network usage over the last hour. It needs the `VM.Audit` privilege, and is only read while the tab is shown.

The arrow at the end of the tabs collapses the bottom panel to its tabs; clicking a tab opens it again.

### Token-based authentication

The Token-based authentication uses an API key without expiration.

1. Open Remote Desktop Manager.
2. Add a new entry.
3. Go to ***Session*** and select ***Proxmox dashboard***.
4. Enter the URL of the Proxmox server.
5. Select ***Token*** as ***Authentication mode***.
6. Type the ***Username*** under which this token will authenticate.
7. Select the ***Realm***, which is the authentication backend.
8. Enter the unique identifier for the ***Token id***.
9. Type the token secret value used for API authentication.
10. Click ***Add*** to save and close the window.

### Ticket-based authentication

Ticket-based authentication uses a username and password to establish a session that remains valid for two hours, with an automatic refresh occurring two minutes before expiration.

1. Open Remote Desktop Manager.
2. Add a new entry.
3. Go to ***Session*** and select ***Proxmox dashboard***.
4. Enter the URL of the Proxmox server.
5. Select ***Ticket*** as ***Authentication mode***.
6. Type the Proxmox account under which this token will authenticate.
7. Select the ***Realm***, which is the authentication backend.
8. Enter the password.
9. Click ***Add*** to save the entry.


---

# 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/how-to-articles/proxmox-dashboard-entry.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.
