Search results

  1. J

    PVE nach Update nicht mehr erreichbar

    Ohne Details zu kennen, sind "Updates" eigentlich "nur" Debian Pakete, die letztlich Files im Dateisystem ersetzen, hinzufügen, entfernen. Wenn bspw. eine Bibliothek schon geladen ist, kann das Betriebssystem weiter laufen und lädt erst bei einem neuen Call die aktualisierte Bibliothek nach...
  2. J

    POLL: Current Firewall Design, what is your ...

    Best would be to upload a drawing of your setup and networks to understand and help you better. Still don't know if I got everything right, but why don't you use VLANs and Virtual IPs? It's difficult and too time consuming to discuss this on a generic level. Please provide some concrete...
  3. J

    POLL: Current Firewall Design, what is your ...

    The easiest, if you have dedicated NICs, is to go for a physically separated "Management LAN", which handles all the HTTPS connections on port :8006. This dedicated LAN can be used to separate traffic completely and thus makes it easy to manage firewall rules. With regard to your second...
  4. J

    POLL: Current Firewall Design, what is your ...

    OK, so I am a non-professional, to be clear upfront. I use dedicated firewall appliances (currently OPNsense), running dynamically updated IP + DNS blocklists, (soon) proxy filtering and IDS / IPS (Suricata) on top. I am diving into logging etc. currently, so I am not an expert here. I am very...
  5. J

    Proxmox VE 6.4 available

    Cool! By the way, did you take a look on encryption as well? Booting from an encrypted partition (ZFS / LUKS)? That you actually have to enter the partition's encryption key via terminal (serial / keyboard / server management) or alternatively SSH and only with that the boot process continues...
  6. J

    Proxmox VE 6.4 available

    Yes, that is what I meant. Thanks.
  7. J

    APU.2C4 --> Proxmox V5.2.1

    Hast recht.
  8. J

    Proxmox VE 6.4 available

    Is it correct that a) file replication is also available within PVE, not PBS b) some filesystems cannot be mounted when doing file replication? With some of my VMs it works perfectly, for others I only see the grub partition.
  9. J

    APU.2C4 --> Proxmox V5.2.1

    Doch, auf der Seite siehst du eine Übersicht der Pakete, u.a. auch enthalten sind die, die nanntest. :)
  10. J

    APU.2C4 --> Proxmox V5.2.1

    Das ist ein sehr valider Punkt. Wieso ist das eigentlich nicht vorgesehen? Gut, in Rechenzentren kann man von einer gewissen Sicherheit ausgehen, aber ich vermute zur zahlenden Kundschaft von Proxmox gehören auch viele KMU, die von Systemintegratoren / Administratoren Proxmox eingerichtet...
  11. J

    APU.2C4 --> Proxmox V5.2.1

    Und genau auf so etwas habe ich keine Lust, da diese Fehler / Eigenheiten immer erst nach ein paar Tagen oder Wochen auffallen und man damit unheimlich viel Zeit verbrennt. :D Gut, zugegeben, ich bin auch kein Poweruser von Proxmox sondern interessierter Heimanwender.
  12. J

    Proxmox VE 6.4 available

    That's a game changer for everyone using file storing services within VMs! :eek::eek::eek: Awesome! :cool::cool::cool:
  13. J

    APU.2C4 --> Proxmox V5.2.1

    Macht Sinn. Ist halt charmant, alles aus einer Hand zu bekommen und sich nicht ein "eigenes" Debian + Proxmox "bauen" zu müssen.
  14. J

    APU.2C4 --> Proxmox V5.2.1

    Danke dir Stoiko, habt ihr die CLI Installation im Hinterkopf?
  15. J

    Backup Directory / Datastore from PVE

    Yes, that's also working. Great piece of software. Thanks for providing that for free to us interested home users. :):):):):)
  16. J

    Backup Directory / Datastore from PVE

    Thanks @aaron, its working. :cool:
  17. J

    backup@pbs != root@pam

    I can imagine, but given that PBS is v1.0, it does a lot of things very good already. Thanks for providing such a straightforward and professional software as PVE and PBS for free. OK, thanks. From my day job I know that ENV variables can be quite appealing ... but they introduce a certain kind...
  18. J

    backup@pbs != root@pam

    OK, thanks. That worked. So for everyone else, within the backup directory, there are folder as /vm /ct or /host, depending on the backup type. Within these there are the IDs as /100 /101 etc. and there you find the file "owner" which contains a string of just the owner. Changing this from...
  19. J

    backup@pbs != root@pam

    No, see below. I rebooted. In the first try I entered a wrong password ("test"). In the second try my current password for the root@pam user on PBS. The outputs differ. root@pve:~# proxmox-backup-client change-owner vm/109 'root@pam!pool' --repository 'root@pam@10.1.X.X:pool' Password for...
  20. J

    backup@pbs != root@pam

    Okay, so we're getting closer. :) Thanks so far @fabian! Still something's wrong. root@pve:~# proxmox-backup-client change-owner vm/109 'root@pam!pool' --repository 'root@pam@10.1.X.X:pool' Error: permission check failed. Same output by the way using: proxmox-backup-client list <...> After...