Search results

Verstehe ich natürlich, wie beschrieben war der Fehler hier allerdings eher seltsam. Klingt auf jedenfalls seltsam. Nachdem jetzt alles geht wird es vermutlich schwer nachzuvollziehen, wieso das passiert ist.

I don't disagree. However, using apt over HTTP is fine. That was basically what I am trying to get across. Also, that in this scenario HTTPS is not the end-all-be-all in terms of security and provides fewer additional protections than it may seem at first.

Hi, spannend. Kannst du den dann von 7.3 auf 7.4 updaten und funktioniert dann das Rebooten noch problemlos? Zeigt Grub noch irgendwas anderes an außer „Welcome to Grub!“? Kannst du das System in dem Zustand an-pingen bzw. dich vielleicht sogar via SSH einloggen?

Yeah, in that case this isn't surprising at all. Did you try adding a metadata cache yet [1]? That might help a little, but generally the performance of such a setup will likely always be sub-par. [1]: https://pbs.proxmox.com/docs/installation.html#recommended-server-system-requirements

Hi! that sounds sensible enough to me, however, there may be some more discussion needed here that I am unaware of. Could you open an issue over in our Bugzilla and request the feature there? Thanks! https://bugzilla.proxmox.com/

Hi, can you post the configuration of your VM? You should be able to find it under /etc/pve/qemu-server. There should be a file with a .conf extension and starting with the ID of your VM. Thanks!

As pointed out in the linked thread: Keep in mind that your ISP will also see the IP address of the host you are making the request to regardless of which TLS version is being used. Also, only fairly recent TLS versions support Encrypted ClientHello (ECH). Even that only provides...

Hi, please also be aware that our apt repos come signed with our GPG keys anyway, so realistically adding HTTPS on top of that does not provide much of a security benefit. The reason we use it for the enterprise repos is that you need to authenticate yourself there to prove you have a valid...

Hi, You don't need to install the backup client in the VMs/CTs themselves. Proxmox VE allows you to make backups from the hypervisor's perspective itself. So you simply configure a backup job in Proxmox VE that includes the VMs/CTs you want to back up and you should be fine. This will create...

Hi, did you try reducing the max-worker count in the performance setting to 8 or 4 [1]? That may help with the VMs freezing. The issues regarding 500er errors sound more like a network error or it may be related to your PBS setup. Can you maybe post a part of the syslog from the PBS side...

Hallo, es gibt auch noch diesen Feature Request der auch schon Patches erhalten hat [1], um Notifications etwas flexibler zu gestalten. Eventuell hier auch ein Auge drauf werfen :) [1]: https://bugzilla.proxmox.com/show_bug.cgi?id=4156

Just chiming in here to say this: That's normal. You are using GRUB as your bootloader then (that should be the default unless you are booting a UEFI system with a ZFS root partition). systemd, among other things, acts as the init system in Proxmox, i.e., the process that is the ancestor of all...

Eigentlich sollte der Command mehr oder minder dasselbe machen wie die GUI. Welche Parameter wurden denn genau verwendet?

Das ist vermutlich Teil des Problems, ja! Bitte mach mal die Schritte zum Entfernen einer Node aus dem Manual durch [1]. Evt. hilft das schon und beachte hier vor allem diesen HInweis: Wieso möchtest du den Raspberry Pi den als Teil deines Clusters haben? [1]...

Great, please mark this thread as “Solved” by clicking “Edit Thread” on top and selecting the “Solved” prefix. This way other users can find this solution more easily.

You have two options, you can adjust how you start your Chrome browser to set the --force-dark-mode flag. Or you click on the menu behind the username (in the top right corner) > “Color Theme” > Select "Proxmox Dark”, then click “Apply”.

Yeah, I think you need one file per interface for this to work. Just keep in mind that they should be number prefixed. You can read more in the relevant man page (man systemd.link) [1]. There may be a more elegant way here, though. Sorry I'm currently unsure too. [1]...

Hi, just a small heads-up: Please mark this thread as a “Tutorial”. You can do so by clicking the “Edit Thread” button on top then selecting the “Tutorial” prefix. That should make it easier to find this thread. Thanks!

Ah ok, did you try hwaddress instead of bridge_hw? AFAICT, bridge_hw was used by ifupdown, whereas hwaddress is used by ifupdown2.

Ok can you run pvscan --cache --aay and then run pvs and vgs again. In theory you should be able to see the "pve" VG then. Can you also elaborate on which disk you resized and how?