I am testing DQS at POSTFIX level and works pretty good. what is not resolve at IP lookup level it will catch spam at content level using its Spamassasin plugin .. I really hope there was an implementation for this plugin on proxmox mail...
for the ones with radosgw for S3 if you get 403 when trying to upload new files, temporary disable rgw_sigv4
node-01:~# ceph config get client rgw_sigv4_insecure
false
node-01:~# ceph config set client rgw_sigv4_insecure true
node-01:~# ceph...
the output on ThreadReaper sounds very wrong - it states both grub and systemd-boot are installed on the ESPs, yet there is no Grub config file?
could you please post "apt list --installed | grep -e systemd -e grub"?
root@ThreadReaper:~# apt list --installed | grep -e systemd -e grub
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
grub-common/stable,now 2.12-9+pmx2 amd64 [installed]
grub-efi-amd64-bin/stable,now 2.12-9+pmx2...
So you must use qcow2 files? Big oof due to the envolved performance hit. Or do they setup a lvm/thin pool? This would be a reasonable choice to have a kind of bullet-proof novice-friendly setup.
I suppose a middle ground for your needs is use a front end in front of Proxmox, it has an API system, but even a simple reverse proxy might work, have this front end block root level login's. Then firewall of 8006 to staff. I really would not...
I think this patch you're linking to is aimed at replication. I'm not into HA, so don't deal with clusters. I'm more talking about the checksum errors using snapshots and ZVOLs. Sorry, should have been more clear.
Resolved: GRUB rescue prompt after kernel update — root cause was multi-PV LVM boot
System: Proxmox VE 9.2, UEFI boot, pve VG originally spanning two physical volumes (/dev/sda3 + a second NVMe partition, added earlier via vgextend/lvextend to...
Did you create your hook script on Windows (CRLF line endings)? If so, save in unix file format or convert otherwise.
If it's Windows line endings it's trying to run the script with #!/bin/bash\r (which doesn't exist) instead of just #!/bin/bash.
I installed 0.1.302 on my non-critical cluster earlier today. so far no issues, but it hasn't been long enough to make a decision one way or the other yet. if i run into any issues, i'll update here.
Joining in with the following observations; over a year since last driver refresh, there have been driver updates but no binaries released until now. Upstream changelogs minimal to say the least. This is Not the fault of Proxmox team. We know...
Hello,
we have observed a very rare but serious issue on two different Windows Server 2025 VMs running on Proxmox VE with Ceph RBD storage.
Both VMs are FSLogix profile container file servers with a nearly identical workload.
Windows log shows...
Ran into an edge-case with a PBS virtual machine that had the chunks stored the host, backed by virtiofs. Garbage collection would consistently fail with "ENFILE: File table overflow"
Finding the limit wasn't the easiest since it isn't enforced...
Hi everyone,
it's been a week since I changed the disk settings of all my virtual machines to
Cache: Default (No cache)
and the slow memory migration issue is no longer occurring.
I Have stable speed of migration:
2026-09-22 18:03:56...
For me keepalived is the missing cluster technology to add to Corosync and Ceph and Proxmox HA etc.
I setup my clusters with IPs that start at ...1 and use keepalived to do ...0. The cluster DNS name is pve and the nodes are pve<x>.
VMware...