Proxmox Datacenter Manager - First Alpha Release

kotakomputer said:
Hi Johannes, I think you misunderstanding the issue. Proxmox DM now already support PVE 6 (except PVE 5 because has no Token feature, so I agree with you to ignore this PVE 5 version), you can see PDM has option to use manual API Token in this case, what is missing is: Migration feature. Another feature like Stop and Start already supported for PVE 6.
Click to expand...


Citation needed at least on https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap or in the first post in this thread nothing is said about supported versions. I might have missed a staff statement on this but imho it's more likely that just because something is (barely) working doesn't mean it's supported. And the cli feature remote-migration (with the framework under it) was introducted in 7.4 according to the PVE release notes/roadmap thus I doubt that there are any plans to backport that to older versions. It would need some work with nothing much to gain (because again it's a good thing to discourage people from keeping EOL systems running in production)
 
  • Like
Reactions: UdoB
kotakomputer said:
Suggestion for PDM:

By default PDM Migrate "Delete Source" is True. I think better set it to False. So any VPS that can not run correctly in new server still has its original VPS.
Click to expand...
I disagree. By default it should clean up after itself instead of leaving orphaned bits around.
That said, it it fails to migrate (including not being able to power on) then the process should fail and it would not delete the source.
 
  • Like
Reactions: Johannes S
  • Like
Reactions: flames, SInisterPisces and ThomasGlanzmann
Looks like the auth API changed a bit and I dont receive a ticket anymore but instead an empty "ticket-info".


Do you have some curl examples on how to authenticate on the 0.9 beta version?

Here is the output of the POST to /api2/json/access/ticket when using username/passsword to authenticate. Does the same with root user.

{ "CSRFPreventionToken": "68D0B2C1:2aVIv....", "ticket-info": "PDM:readonly@pdm:68D0B2C1::ticketinfo", "username": "readonly@pdm"}

I can't use the empty ticket to authenticate and ask for a resources list for example, getting following error.

authentication failed - ticket with bad signature: error decoding base64 data

Was working fine on 0.0.11 Alpha using the root user.
 
  • Like
Reactions: flames, waltar and muhammad_05
I came back again, but with a review. Thanks for such a great tool, I got the necessary migration function during testing today. I would like to see some small improvements in the system. When there are several clusters to manage, it is very inconvenient to work with hosts and VMs themselves in the remote section, since the management window is very small. it would be great if it were possible to configure a window so that all virtual machines of a node or cluster could be displayed in one window. t
 
for example, you can collapse the dashboard with statistics and expand the dashboard with hosts and virtual machines
 
New install of PDM 0.9.1 Beta.

When I try to add my PVE server nodes to the "Remotes section of PDM I get an error in the endpoints tab that states "pvehostname - api error (status=400: client error (Connect)) for three other PVE server nodes that are auto-detected after entering the initial node IP address and fingerprint in the "Probe Remote" tab of the "Add Remote" window.

If I remove the three auto-detected nodes (endpoints) shown with host names not IP addresses, from the list, the process completes successfully, However, the node does not show up in the remotes list.
Any ideas on what I may be doing wrong, or what I can do to correct the issue?

New PSM vm installed from latest ISO, and all updates applied. Multiple reboots to try and "burp" the settings change to take effect.
 
Last edited:
cjonesinbgwa said:
New install of PDM 0.9.1 Beta.

When I try to add my PVE server nodes to the "Remotes section of PDM I get an error in the endpoints tab that states "pvehostname - api error (status=400: client error (Connect)) for three other PVE server nodes that are auto-detected after entering the initial node IP address and fingerprint in the "Probe Remote" tab of the "Add Remote" window.

If I remove the three auto-detected nodes (endpoints) shown with host names not IP addresses, from the list, the process completes successfully, However, the node does not show up in the remotes list.
Any ideas on what I may be doing wrong, or what I can do to correct the issue?

New PSM vm installed from latest ISO, and all updates applied. Multiple reboots to try and "burp" the settings change to take effect.
Click to expand...

Feels like a firewall issue. Can you ssh (or from it's console) into pdm server and then run:

# echo "GET /" | socat stdio TCP4:pve.host.domain:8006

and it should output something like:
HTTP/1.0 400 bad request
Cache-Control: max-age=0
Connection: close
Date: Mon, 29 Sep 2025 00:52:22 GMT
Pragma: no-cache
Server: pve-api-daemon/3.0
Content-Length: 11
Expires: Mon, 29 Sep 2025 00:52:22 GMT

bad request


If that fails, then figure out your network problem. (Replacing pve.host.domain with the 3 other hosts domains exactly as they were listed in the endpoints when you tried to add them as remotes. (Except add :8006 unless you had some other port being shown, if no port specified then :8006)
 
Last edited:
I installed the ProxMox Datacenter Manager 0.9.1, and I'm trying to determine why it loads fine in Edge but not Chrome, has anyone experienced this? It logs in fine but I only see the top pane. I tried clearing all temporary data, cache, etc. I don't have any extensions loaded.
PDM.jpg
 
Last edited:
rodww said:
I installed the ProxMox Datacenter Manager 0.9.1, and I'm trying to determine why it loads fine in Edge but not Chrome, has anyone experienced this? It logs in fine but I only see the top pane. I tried clearing all temporary data, cache, etc. I don't have any extensions loaded.
Click to expand...
You can open developer tools with Ctrl + Shift + I in Chrome and in the console check for possible errors. It might be some extension that breaks the DCM or some misconfiguration.
 
Hello. Wanted to report (if not reported already) that, after installing latest updates from a fresh install, getting an error when attempting to refresh the updates page:

Code: 
2025-11-24T05:11:24-05:00: starting apt-get update
2025-11-24T05:11:25-05:00: Err:1 http://security.debian.org/debian-security trixie-security InRelease
  403  Forbidden [IP: 146.75.30.132 80]
Err:2 http://deb.debian.org/debian trixie InRelease
  403  Forbidden [IP: 146.75.30.132 80]
Err:3 http://deb.debian.org/debian trixie-updates InRelease
  403  Forbidden [IP: 146.75.30.132 80]
Hit:4 http://download.proxmox.com/debian/pdm trixie InRelease
Reading package lists...

2025-11-24T05:11:25-05:00: E: The repository 'http://security.debian.org/debian-security trixie-security InRelease' is no longer signed.
E: Failed to fetch http://security.debian.org/debian-security/dists/trixie-security/InRelease  403  Forbidden [IP: 146.75.30.132 80]
E: Failed to fetch http://deb.debian.org/debian/dists/trixie/InRelease  403  Forbidden [IP: 146.75.30.132 80]
E: The repository 'http://deb.debian.org/debian trixie InRelease' is no longer signed.
E: Failed to fetch http://deb.debian.org/debian/dists/trixie-updates/InRelease  403  Forbidden [IP: 146.75.30.132 80]
E: The repository 'http://deb.debian.org/debian trixie-updates InRelease' is no longer signed.
W: Skipping acquire of configured file 'pdm-no-subscription/binary-amd64/Packages' as repository 'http://download.proxmox.com/debian/pdm trixie InRelease' doesn't have the component 'pdm-no-subscription' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'pdm-no-subscription/i18n/Translation-en' as repository 'http://download.proxmox.com/debian/pdm trixie InRelease' doesn't have the component 'pdm-no-subscription' (component misspelt in sources.list?)
W: Skipping acquire of configured file 'pdm-no-subscription/i18n/Translation-en_US' as repository 'http://download.proxmox.com/debian/pdm trixie InRelease' doesn't have the component 'pdm-no-subscription' (component misspelt in sources.list?)

2025-11-24T05:11:25-05:00: TASK WARNINGS: 1
 
that sounds like a problem at/with Fastly (Debian's CDN), or a proxy on your end, and not like anything we could fix..
 
I've updated the DCM from the Alfa to the Beta release. We have updated the certificates on the cluster nodes. I've included this information in the cluster configuration on DCM, but in the proxmox-datacenter-api.service, it still uses the old fingerprints. Service restarts and DCM VM reboot didn't help.
In the WEB UI the fingerptint configured is c4:d4:02:17:3f:3a:cb:ba:a9:fa:25:c9:2d:f4:4e:65:3c:7f:5f:fd:50:d7:9a:ad:c2:20:92:78:f8:a9:29:12
But it seems to have no effect.


pm-dcm proxmox-datacenter-api[662]: failed to query info for remote 'cluster' node 'host420.aone.local:8006' - client error (Connect)

Caused by:
0: client error (Connect)
1: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:2123:
2: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:2123:
pm-dcm proxmox-datacenter-api[662]: bad fingerprint: 47:69:ef:da:f8:1d:9d:e9:ca:34:29:85:90:26:54:39:8e:6e:ad:7a:bc:b3:55:fe:a3:98:5a:6d:70:47:04:98
pm-dcm proxmox-datacenter-api[662]: expected fingerprint: c4:d4:02:17:3f:3a:cb:ba:a9:fa:25:c9:2d:f4:4e:65:3c:7f:5f:fd:50:d7:9a:ad:c2:20:92:78:f8:a9:29:12
 
did you maybe mix up some certificates/nodes/fingerprints? the error message says that the remote has a different one than you configured.. note that if you use Let's Encrypt or another trusted-by-default CA, you don't need to provide a fingerprint at all, you can just use the FQDN as endpoint and it should work.
 
unable to install step 3

root@pve6:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
proxmox-datacenter-manager : Depends: libapt-pkg6.0 (>= 1.9~) but it is not installable
Recommends: proxmox-datacenter-manager-client but it is not going to be installed
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. proxmox-datacenter-manager:amd64=0.1.12 is selected for install
2. proxmox-datacenter-manager:amd64 Depends libapt-pkg6.0 (>= 1.9~)
but none of the choices are installable:
[no choices]
root@pve6:~#

pveversion
pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.17.2-1-pve)
 
Last edited:
pavlos said:
unable to install step 3

root@pve6:~# apt install proxmox-datacenter-manager proxmox-datacenter-manager-ui
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
proxmox-datacenter-manager : Depends: libapt-pkg6.0 (>= 1.9~) but it is not installable
Recommends: proxmox-datacenter-manager-client but it is not going to be installed
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. proxmox-datacenter-manager:amd64=0.1.12 is selected for install
2. proxmox-datacenter-manager:amd64 Depends libapt-pkg6.0 (>= 1.9~)
but none of the choices are installable:
[no choices]
root@pve6:~#

pveversion
pve-manager/9.1.1/42db4a6cf33dac83 (running kernel: 6.17.2-1-pve)
Click to expand...
You very likely have a broken apt sources configuration! Please check that out, ensure they all use same distro (bookworm for pdm0/alpha, trixie for pdm1/beta), and if you cannot figure that out, or if something else is off too, then please open a new thread, the generic alpha release thread is not the right place to debug this.
 
You must log in or register to reply here.
Top Bottom