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)
Proxmox Datacenter Manager - First Alpha Release
- Thread starter t.lamprecht
- Start date
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)
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.
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.
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.
For reference, and to avoid duplicate work, this was already answered in the other thread: https://forum.proxmox.com/threads/proxmox-datacenter-manager-0-9-beta-released.171742/post-802941
Please avoid double posting in the future.
Yes, you can follow the issue here https://bugzilla.proxmox.com/show_bug.cgi?id=6793 to get notified once it's available.
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.
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:
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:8006and it should output something like:HTTP/1.0 400 bad requestCache-Control: max-age=0Connection: closeDate: Mon, 29 Sep 2025 00:52:22 GMTPragma: no-cacheServer: pve-api-daemon/3.0Content-Length: 11Expires: Mon, 29 Sep 2025 00:52:22 GMTbad requestIf 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: