Search results

do you have any firewall/proxy in between the vm and your workstation? (just to be sure: did you prepend the ip/domain with 'https' ?)

yep, this is a regression, i sent a patch today for this: https://lore.proxmox.com/pve-devel/04308263-4da1-4afc-8789-b868f5e49431@proxmox.com/T/#t

can reproduce the issue, but only when the datastore has an error. What does the content tab on the PBS gui show ?

it depends on what you want pdm to do. In essence, the pdm token for the pve cluster needs the same permissions for it's action as when you do it on pve directly. e.g if you want to start/stop vms, the token needs the VM.PowerMgmt permissions (or higher) for those vms. if you just want a...

thanks i could reproduce it here, and sent a patch: https://lore.proxmox.com/pve-devel/20251205091539.783566-1-d.csapak@proxmox.com/T/#u

did you clear the browser cache? was it the new datacenter bulk migration or the per-node one?

this was fixed very recently: https://lore.proxmox.com/pdm-devel/20251126131859.2745340-1-d.csapak@proxmox.com/

what version of pdm and pve do you use ?

Hi, im Web UI gitbt's den punkt 'remove' unter tape backup -> inventory. Da das tape nicht mehr vorhanden ist wird man wohl das 'force' flag aktivieren müssen um es zu entfernen. Hoffe das hilft!

what exactly do you mean? the patch to configure read threads for tape backup jobs are in since 3.3.5, you may have to adapt your backup jobs though

this looks weird and maybe unrelated, can you post the versions of the pdm and pve here? what user are you logged into with at the pdm ?

the question is why is there a token with that name already? is there something/someone that is using that token? if you really want to clear it, there are 3 possibilities: * you go to the pve ui and delete the token -> every user of that token will not be able to connect anymore * use a...

you can't really "clean" the task logs, since they're not meant to be deleted, rather than simply display the results that exist as soon as the task logs are outside the given timeframe (48h according to your screenshot) they will not be shown there anymore

you can of course open a feature request for this, but no promises that it'll be done (or when) one of the problems in implementing this is that the task logs are saved on the local filesystem on each node, so not easily accessible from the other nodes. And we usually don't do api calls that...

sent a patch now: https://lore.proxmox.com/pve-devel/20251119092634.763388-1-d.csapak@proxmox.com/T/#u

hi, i guess this is an ECC key? in that case the minimum size we check against is 224 not 2048, but the log line has the 2048 bit hardcoded ;) i'll send a patch as it's confusing

i think you misunderstood me: the list is still sorted by name, but the individual entries are wrongly rendered (vmid before name) anyway, thanks for reporting, i sent a patch that should fix it: https://lore.proxmox.com/pve-devel/20251117131945.2148025-1-d.csapak@proxmox.com/T/#u

it's still sorted by name: 108 Arch-Budgie comes before 102 Arch-Cinnamon but the rendering is wrong (vmid before name). I'll look into it

no currently migrations (be it intra or cross cluster) will not use the network to the pdm, but either * the normal cluster migration network (intra cluster migration) * the path the source cluster would take to the ip/name the pdm knows of the target cluster (so the source will resolve the...

You can also opt to only given the Datacenter Manager a token with limited access rights, e.g. audit only. PDM will not be able to *do* anything, but you can still monitor it and get quick access with a link.