Thanks, I will start with PBS installing on the Intel NUC with 8gb ram and 110gb ssd after that is working i'll come back to you to explain me please how to setup the 2nd machine as cascade.
Try to completely disable c-states in bios.
Could be a storage problem too, try disabling sata link power management in bios, or for testing everyting related to power saving.
And check what nic you have, if it is a intel you maybe affected by...
Hi @pavlos , this is because you have not purchased support subscription and are not authorized to connect to ENTERPRISE.proxmox.com.
Follow the steps to disable the Enterprise repo and to enable the no-subscription repo...
As the title say. I have ok speed to the remote, 50-70Mb/s but the ping is high. Trying to add one pve and one pbs but get same error: api error (status = 400: client error (Connect)). The error pop up directly, I would say in a shorter time than...
Afternoon everyone, so I have a question which is if it’s alright to install the base proxmox OS and node on a m.2 SATA SSD Won’t be running anything heavy just some home stuff.) I will use an enterprise grade SATA drive for the VMs but for the...
Hello All,
I am attempting to restore a VM from a PBS instance that has some amount of corruption in the underlying files. Output from a restore attempt is some version of this:
restore failed: Failed to parse chunk...
Figured I'd take the time to dump some detail on why the VM borked under the 6.8.12-16-pve kernel. (Seems like it was the SATA controller I use to passthrough a bluray optical drive.)
journalctl --since "2025-11-26 09:48:05" --until "2025-11-26...
I am doing the same with immich, but got a Problem. The share is accessible via cli and user root. But not with immich. No read permission. Can you give me a hint?
There is no user "immich" to authorize to tha share.
I have little knowledge about PVE clusters, but I would say yes. Usually it's recommended to run newest PVE and PBs versions.
From your screenshot "Add: Proxmox Backup Server" I understand that you add it as the root user.
A safer method is NOT...
You can delete the api token under datacenter>permisions>api tokens for the node that you added. I had the same error when adding a cluster and couldn't find the secret that was created for the api token.
Nimm das proxmox-boot-tool.
Da siehst du alle installierten Kernel und kann mit der Option pin den gewünschten Kernel anpinnen. Eventuell auch mal den aktuellen CPU microcode installieren.
Hi all,
I saw a bit higher spam level lately, I went to inspect the spam report inside the headers and found:
X-SPAM-LEVEL: Spam detection results: 2
BAYES_50 0.8 Bayes spam probability is 40 to 60%
DKIM_SIGNED...