No - the permission system in PMG is not domain aware - and for a very large part of the administration/configuration the settings are global (e.g. rules, most postfix configuration,...)
I hope this helps!
Contributions are very welcome - thanks for the suggestion!
We use a mail-based workflow - see https://pve.proxmox.com/wiki/Developer_Documentation for submitting patches.
from a quick look at the code: https://git.proxmox.com/?p=pve-container.git;a=blob;f=src/PVE/LXC/Setup/Base.pm;h=dbfc775c6f4769609c50caa6c8a7b91a91566080;hb=HEAD#l294
It should be set to true, if you set the containers IPv6 config to 'auto'...
send a patch for this just yesterday: https://lore.proxmox.com/pbs-devel/20250818194026.840749-2-s.ivanov@proxmox.com/T/#u
:)
Thanks for the report in any case!
Just a nitpick running pbs3to4:
SKIP: System booted in legacy-mode - no need for additional pacckages.
should be
SKIP: System booted in legacy-mode - no need for additional packages.
(One less c in packages!)
see: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine - v320.pre is handled by the templateing system.
I hope this helps!
Yes! (systems not using proxmox-boot-tool should have it mounted on /boot/efi)
proxmox-boot-tool is (currently) used for all installations which are not using Ext4/XFS (with LVM) - it was initially added to handle ESPs for machines with multiple...
See: https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine - the postfix configuration is done via templates.
127.0.0.1 is also called the loop-back ip (localhost) and is e.g. used to speak with services on the same...
don't think that it's related to IPMI/Server board vs. Desktop board - but maybe it's something related to when the servers were setup - or secure-boot related... - do you happen to remember when you set them up? - and does `dmesg|grep -i secure`...
term.log received via different channel.
from the one you sent - looking through the large output - you can find:
Installing for x86_64-efi platform.
grub-install.real: error: cannot find EFI directory.
Failed: grub-install --target=x86_64-efi...
Hm - could I ask you for the term.log from the dist-upgrade in this case?
Maybe you ran into something we haven't considered yet - or something we could add a warning about to pve8to9 (and thus help users who yet have to upgrade)
Thanks!
After a Debian update, my PMG cluster is no longer synching. Main node is active and the two nodes are always in 'synching' state. Syslog keeps on showing on both nodes:
pmgtunnel[4515]: status update error: command 'ip -details -json link show'...
The instances were setup on top of Debian. These are Cloud VMs at Hetzner if this matters. Running since at least 2,5 years without any problems until now.
root@mx01:~# pmgcm status...
I think I found the issue and prepared a patch: https://lore.proxmox.com/pmg-devel/20250818131333.13364-1-s.ivanov@proxmox.com/T/#u
However
I'd still recommend to add an entry to your /etc/hosts which points your local hostname to a...
Thanks for adding the output and reporting that you're affected as well!
hm - did not manage to reproduce the issue here locally...
Could you additionally provide:
* the complete output of `pmgcm status`
* the contents of `/etc/pmg/cluster.conf`...