Search results

I had conflicting container id on my sites this was causing my confusion

So I have site a and b both have a pve and pbs server on them. My goal is to use them for each others offsite. I am currently backing up pve @ site a to pbs@site a and pve@b to pbs@b I have a sync job the runs nightly for both site a and be targeting the other. Now trying to work backwards...

I connected the networks using tailscale when i do my dataset scan now i get a tcp deadline has passed error. i am open to any other clever ideas for dealing with instances that are behind cgnat and port forwarding isn't an option

So I am not connecting my sites with wireguard as the sites don't have the ability to control their own ports. But I agree that approach makes a lot more sense. In case anyone finds this the issue turned out to be exactly what was purposed. Caddy is a layer 7 http server so it doesn't have the...

I am using caddy to reverse proxy to my lan from my VPS in order to create a offsite backup using remote sync. I use wireguard to connect my vps to my home hence to avoid exposing my ip directly. I set up acme certs on proxmox backup server so that it had a real cert. But when i go to sync my...

proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.44-2-pve: 5.4.44-2 pve-kernel-5.3.18-3-pve: 5.3.18-3...

Each time I attempt to connect with a spice viewer these errors show in the log. The memory error has been there I just need to pull the stick I believe Feb 03 16:41:30 lightmedia QEMU[9349]: kvm: warning: Spice: error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca Feb 03 16:41:30...

When you say from the vm you mean the log from inside that installation correct if so no. These are displayed in my node kernel log I did go through and make sure all the memory DIMMs are installed correctly this briefly stopped the error from coming back but 24 hours later it was back. Would...

Thanks man deleting the db then restarting the service has gotten it.

So I cannot remain logged into my web GUI for more than a few minutes and I think this could be the culprit. Dec 22 14:33:00 lightmedia systemd[1]: Starting Proxmox VE replication runner... Dec 22 14:33:01 lightmedia systemd[1]: pvesr.service: Succeeded. Dec 22 14:33:01 lightmedia systemd[1]...

The Issue turned out to be improperly install ram

Can someone help point me in the direction of what this error might be created by as I think this is what is causing my vm instability

One of my virtual machines keeps rebooting randomly at night, but i cannot seem to make head or tails of the error log. 12/18 @ 2:03 12/18 @ 5:14 these are my crash times from today I have attached my kern.log

I pulled a nic card out of my server and swaped the Linux bridge to a new port. Upon booting back up my system date is stuck at 2042 and cannot connect to a ntp server