please do not double post.
i have answered to your first post.
whether it's "enough" of a measure to protect your instance, depends entirely on the rules you set up on the firewall itself and your network configuration.
you don't have to use pfsense VM for firewalling. you could also use the proxmox FW or hetzner/ovh/any firewall solution for that matter.
if you add source-directory /etc/network/interfaces.d in the configuration file, other configuration files you add into /etc/network/interfaces.d/ will affect your network configuration.
it's not recommended to edit this file manually, so instead use GUI or in case you have specific...
the security.* namespace is reserved for root, so it won't work with unprivileged containers (privileged containers run as real root so they don't have this restriction)
unfortunately it seems like samba uses security.NTACL  instead of a userspace implementation. you could try setting...
würde ich vorschlagen. einfach ein backup erstellen, und beim restore die checkbox auf 'unpriviligiert' aktiviert lassen.
was für probleme kriegst du eigentlich momentan? nur die lan verbindung? vielleicht können wir uns anschauen und einen workaround finden.
ja... ich glaube debian buster...
is this really the entire output? you should be seeing a lot more. can you post the full output?
pipe the output to a file like this:
journalctl -u 'pve*' -e > journal.txt
and copy/attach the journal.txt file
yes. host-only adaptor is for communication between your machine and the proxmox vm.
in your screenshot i see you have a weird network config. gateway from 10.0.3.2 won't work with the IP address you've set.
it starts with a problem in the container which doesn't start properly.
basically, systemd kills the cleanup process before it can do its job, a bit racy.
you could start your container with debug logs and we can take a look why it doesn't boot.
these directories are left behind when a container fails to start and doesn't clean up properly afterwards.
did you upgrade from old debian like wheezy? because newer debian versions use systemd instead of init, and upgrading from such versions seem to cause inconsistencies w.r.t...
you have same MAC address 12:1B:4D:FD:B6:F7for both VMs. maybe that's why you don't get network connection.
however i think the problem can be because of the power disconnect. it's likely that your disk got corrupted or the lvm metadata was deleted.
not possible to tell without the output...
we don't use openvz for containers anymore, we use lxc.
you can use our tool pveam to fetch templates, or you can go to http://uk.images.linuxcontainers.org/images/ and get the rootfs from there and create a new CT with it.