Proxmox Datacenter Manager - First Alpha Release

[CLE]

I created a remote server, but because I didn't like the ID I removed it.
Now I want to create it again but I keep getting the error message that the token already exists.
How do I delete it completely so that I can create it again

Error:
api error (status = 400 Bad Request): error creating token: api error (status = 400 Bad Request): Parameter verification failed. tokenid: Token already exists.

C

[SOLVED] Thread 'I added a remote node but then noticed a typo and removed it, I cannot re-add it I get below error'

Friday at 15:28

api error (status = 400 Bad Request): error creating token: api error (status = 400 Bad Request): Parameter verification failed.tokenid: Token already exists


How do I use existing token or delete the one that's already there?

• Curt Hall
• Replies: 2
• Forum: Datacenter Manager: Installation and configuration

 

[RocketSam]

Just as a heads up to the devs and users who want ot update from 0.1.7 to 0.1.8
Do it via direct access and NOT VIA THE WEB SHELL.

When updating via the upgrade button or web shell it will terminate the shell after:
Setting up proxmox-datacenter-manager (0.1.8) ...
proxmox-datacenter-manager-daily-update.service is a disabled or a static unit not running, not starting it.

This causes APT to also be terminated and thus not finish the update fully.

I confirm this. I've updated via GUI. An the result

 

[masteryoda]

Good start and now i have 1 place where i can monitor all my pve hosts. caught a bug and posted it separately.

 

[Jean-Paul van Hamond]

I installed PDM today and tested it across several clusters. My primary clusters consist of at least 10 hosts, but for the Alpha test, I added three clusters. Here are my findings so far:

1. I frequently encounter the error: "NetworkError when attempting to fetch resource".
2. When moving between clusters, I receive the message: "VM xxx already exists". It seems that fetching the next free VM ID does not work correctly in the target cluster during migrations.
3. There appears to be an issue with remote web links. All my clusters use FQDNs, but the links to the web interfaces or shells only display hostname:8006.


Suggestion for Improvement:
It would be great if folders or locations could be created under the “remotes” section. We use multiple clusters per physical location, and in some cases, standalone PVEs are used at these locations due to licensing requirements. A folder structure with 2 or 3 levels would work perfectly for organizing this setup.

Let me know if further details or logs are required to assist in addressing these issues.