Search results

That's exactly what I'm talking about in the local namespace. you choose any one, and it syncs to the first one on the list

I noticed that even if you select the second or third namespace, the synchronization job still goes to the first one from the top

i know that's why I suggest in the process of transfer also periodically re-requesting the real value

hi, during the transfer of the virtual machine, along with the contents of the RAM, an incorrect value of the transferred data is displayed. It turns out that it ended up being transferred more than it was originally. I propose to do the same as in any rsync operation: in the process of...

the question here is not history or monitoring, but visibility. Dashboard actually created for the general informativeness. I also do not have access to the CPU load history for example

i find excellent issue but, after upgrade node i need try setup it. I think that the output of these data would be useful to everyone. I propose to add this solution to the roadmap

yes, its work.

hetzner_dns not work in ver 7.1 where is code in file: /usr/share/proxmox-acme/proxmox-acme ? two function not found and api plugin not work: dns_hetzner.sh: line 154: _readdomainconf: command not found lost functions i get from original file acme.sh #_readdomainconf _readdomainconf() {...