i found this error !
root@pve:~# apt autoremove
REMOVING:
proxmox-kernel-7.0.2-6-pve-signed proxmox-kernel-7.0.2-7-pve-signed
Summary:
Upgrading: 0, Installing: 0, Removing: 2, Not Upgrading: 0
2 not fully...
Dear Promox,
please reconsider your concerns about subject logging.
Yes it can be problematic in relation to the GDPR, but in principle every admin with system access can read all forwarded mails (eg. a simple bcc can to the job or modification...
Hello BobhWasatch,
thank you for your info,
however, as you mentioned above, mean all clients always rejected not follow as NTP server on master node in local.
So, if we start disable the below option do the client node will synchronizing with...
I'm not interested in using an AI agent at all on my hosts because my data is too important for me: https://www.euronews.com/next/2026/04/28/an-ai-agent-deleted-a-companys-entire-database-in-9-seconds-then-wrote-an-apology
In other words: I...
I'm not interested in using an AI agent at all on my hosts because my data is too important for me: https://www.euronews.com/next/2026/04/28/an-ai-agent-deleted-a-companys-entire-database-in-9-seconds-then-wrote-an-apology
In other words: I...
I'm not interested in using an AI agent at all on my hosts because my data is too important for me: https://www.euronews.com/next/2026/04/28/an-ai-agent-deleted-a-companys-entire-database-in-9-seconds-then-wrote-an-apology
In other words: I...
Hi @cyruspy , you did not mention what SAN you are using. If its a Hitachi compatible with the mentioned plugin - that should, hopefully, work. Otherwise, you should use vendor-specific plugin, if one exists for your storage.
Cheers...
Just tested with: Linux pve-homeserver25 7.0.12-1-pve
Can report the fix is in and Tailscale speeds are back to what they were, without needing any workarounds - huzzah!
11:18 user@samba:~ > iperf3 -c <host-b-tailscale-ip> -t 10
Connecting to...
Thanks for this guide. I just got my Quadro P4000 working. It didn't like kernel 7.x or 6.17, but 6.14 worked like a charm. NVIDIA Driver 575.57.08 installed, and the device was able to pass through to my jellyfin container successfully
I had the same issue and fixed it issuing following commands one by one:
NOTE: sda2 and sdb2 are the efi partitions of the two disks I have on this particular system
proxmox-boot-tool clean
proxmox-boot-tool format /dev/sda2 --force...
the VLAN SDN zone already does the clusterwide syncing heavyweight lifting. nothing stops you from creating a script that polls VLAN list from the external source and uses native CLI tooling to add VLAN entries. Then, cron is your friend :)