Search results

I've noticed that since updating to proxmox-backup-client 2.3.1-1 that the command: proxmox-backup-client task log <UPID> --repository <user>@<PBS IP address>:<datastore> no longer outputs to STDOUT. I've found that I now need to add 2>&1 after the command to redirect the output from stderr to...

That all looks correct to me, I don't see any config issues. If you're trying to get it to work outside of your network, have you made sure to port forward TCP port 3128 to your nginx reverse proxy server? Your proxmox config file in Nginx will be irrelevant to getting spice to pass through the...

Here is the solution: I went down a rabbit hole for this.... Your above configuration is running in layer 7 (application layer) and we need to run in layer 4 (transport layer) I'm using debian, so some things may vary with things like sites-enabled/sites-available package names etc, but the...

I converted from seabios to ovmf and backedup three times now, once manually. During the conversion I had copied my raw VM disk to a fresh VM. Since doing this I haven't had the issue. I'll continue to monitor, but it may be solved for me. Hopefully this helps someone else that stumbles into...

For me, the issue appears to come up when backups are being taken at night. I've also noticed its always the same virtual machine, this is also my only BIOS virtual machine, all others are UEFI. The virtual machine doesn't respond to qm stop <vmid> and if I try running systemctl stop...

I started having this problem recently on 6.2 after changing my storage to be ZFS on the proxmox host rather than LVM on iSCSI. I upgraded to 6.3 yesterday and am having the problem again this morning.