Search results

Thanks Fabian. That was the issue :-) I edited the file /etc/pve/nodes/pve/config to add the alias=xyz.com. And it's now working! # cat /etc/pve/nodes/nuc/config acme: account=myaccount acmedomain0: pve.xyz.nl,alias=xyz.com,plugin=cloudflare # pvenode config get acme: account=myaccount...

I think the issue in my case is with challenge-alias: - If I use a domain that is directly hosted in Cloudflare then it works fine. - If I use a domain that is hosted at a provider that doesn't support API provisioning (xyz.nl), then I create a CNAME record _acme-challenge.pve.xyz.nl pointing to...

I have the same problem. This used to work in proxmox v8, I'm now on v9 and it's broken I think. - In the GUI I can create an account - I want to view it, but the windows shows no details - I can create a plugin using Cloudflare DNS - When I try to get the certificate I get also the following...

I had the same error. I was using keycloak with certificates from zerossl, that I generated using acme.sh. The issue is that Proxmox doesn't have the CA yet. So I had to copy the zerossl CA to /usr/share/ca-certificates and run the dpkg-reconfigure ca-certificates. Afterwards my proxmox-keycloak...

Thanks a lot for sharing this! I was trying to get a VXLAN working between 2 remote sites connected via wireguard using this EVPN SDN and it wouldn't work. I modified /etc/frr/frr.conf on all my nodes and all is working now :)

Correct, DHCP is only working for simple as far as I know, it will be there in the future for other zone types. What is your goal? To test SDN or to make a VM running on different nodes? If your goal is to have VMs communicating between eachother then you don't need SDN, you just need to...

Did you create a simple zone? This type does not allow communication between nodes. See https://pve.proxmox.com/pve-docs/chapter-pvesdn.html#pvesdn_zone_plugin_simple

Hi All, I have 2 home locations: site1 and site2: - Site1 has a pfSense router with a Public IP and a 2 subnets: 192.168.1.0/24 and 192.168.10.0/24 - Site2 has a unifi gateway max with also a public IP and 2 subnets: 192.168.2.0/24 and 192.168.20.0/24. I managed to create a wireguard Site to...

Hello, I have the following issue: I tried to replace an old 2TB nvme disk wich is hosting all my VMs. I had a 4TB SATA drive which I added to my single ZFS pool. This worked fine, but I still had my pool in DEGRADED status. I decided then to get another 4TB drive and add it as a replacement...

I have a single disk pool for all my VMs called "storage". The nvme 2TB disk gives errors, so I bought long ago a SATA 4TB disk to replace it. I added the disk to the pool to create a mirror. But the pool was still in degraded mode. So I bought the same 4TB disk to make it a mirror and replace...

Actually the workaround (spotted by Robson earlier in this thread) to set the CPU type to Host instead of Default (kvm64) solves the problem. But using the default doesn't while is used to work with previous Stream 9 isos.

I'm encountering the same issue with the new CentOS Stream 9 ISO. I've tried it on 2 proxmox nodes, one based on Intel and the other one AMD. The same works fine using a previous CentOS Stream 9 ISO from Begining January. It also works fine using the latest RHEL9 Beta. It would be interesting...

Same here, Thanks for the tip, I've been busy hours on this and was about to reinstall and lose all my LAB VMs. I summarize the solution here: https://forum.proxmox.com/threads/upgrade-pve-6-x-to-7-x-grub-issues.92118/post-429676

I had exactly the same issue and I've been busy the whole day to fix this. The solution was as follow: - Execute all the steps from here: https://pve.proxmox.com/wiki/Recover_From_Grub_Failure - the update-grub will fail. At this point you need to lvextend your logical volume with 2G for...