Search results

I solved it by launching the build in uefi shell of my server and startet grubx64.efi by hand, it looks like the boot entry tries to boot bootx64.efi which does not work for some reason. I did a grub reinstall and hope the next boot works without interruption.

Same issue with Proxmox Enterprise.

You can get a almost working image from https://fra1lxdmirror01.do.letsbuildthe.cloud/images/ubuntu/noble/amd64/default/ (rootfs.tar.xz), but you have to remove the yml file from /etc/netplan directory.

Hi Fiona, good to know. I ran 24.04. from linuxcontainers.org before i pulled pve-containers from pvetest and using the official template. The templates from linuxcontainers.org almost work out of the box including console except network, i had to remove netplan yml config from /etc/netplan if...

pve-container 5.1.10 alone is not enough, network and console does not work with 24.04. containers.

PBS maintanance does lots of reorganization and disk writes, that is the reason for SSDs in PBS. Cheap / non enterprise SSDs will wear out quiete fast.

I know your pain, same happend to me and not just ones.

We are on 7.4-3 here, no issues with Azure AD or Keycloak (two different installations). If it never worked, check your client id and key again.

Normaly acme likes environment variables like: AZUREDNS_SUBSCRIPTIONID="..." AZUREDNS_TENANTID="..." AZUREDNS_APPID="..." AZUREDNS_CLIENTSECRET="..." But i never used the acme Azure Plugin in Proxmox so give it a try, maybe line by line or delimited with ; or ,

Auf deinem System ist bestimmt cfdisk installiert und ich glaube auf CentOS 7 unterstützt cfdisk es auch schon extend/erweitern, das ist deutlich einfacher als sich mit fdisk rumzuschlagen.

Es sind drei Schritte erforderlich: * Virtuelle Platte vergrößern * Partition oder LVM vergrößern * Dateisystem vergrößern Ich glaube bei dir fehlt der zweite Punkt.

Installier dir mal die inotify tools mit "apt install inotify-tools" und dann schau mir "inotifywait -mr /zPool/postgres" was da so passiert. Inotify zeigt dir alle Dateisystem actions an.

And today this issue is back, i took a quick look into pveproxy/access.log. I can see there is a callback which starts with ?code=... and a long string which is about 1066 bytes long, followed by some more stuff like state=, session_state= and so on. Maybe the issue is that code= is over 1024...

Hi, i get that "code: value may only be 1024 characters long." sometimes, it appears and disappears from time to time.

ah yes, and i fixed it. Error on my side. i reconfigured it and used key id and not secret for the secret. It works now. Thank you. Ps. Works on both, PVE and PBS.

Hi Mira, i just installed this version on one of my non-subscription hosts, i restarted pvepoxy (dont know if required) but AzureAD still fails with 401. Autocreate is on so this should work. --2022-04-20 11:24:24--...

Patch suffix looks like rust, i think without a full pve development environment we cant to anything with that diff by ourself because rust stuff has to be compiled.

I am sure that the Debian version under PVE 5.x is no longer supported. If your environment is not 100% air gapped, then this is a very bad security practice.

I would recommend using a single 10g, less power usage and a single connection can use as much bandwith this physical connection provide. In my home setup i have two Proxmox hosts and one OPNsense Firewall connected via 10g, i do a cross backup between these two hosts where 10g helps a lot. As...

I setup my new network today and i wanted to use vxlan at home to learn more about vxlan and Proxmox using SDN. So i got a new switch and rebuild my network today, my configuration looks like this: Aruba 2930F, default VLAN is jumbo with and mtu of 1550 and max-frame-size of 1568 Proxmox 7.0...