Back to the original question about installing NUT manually.
I had the chance this week to set up NUT for two separate UPS units, one on USB, one on an APC Network Management Card via SNMP. Quick summary of both:
USB: lsusb to get the...
I believe this patch is yet to be merged - maybe an addition to the documentation would be nice as I have just hit this exact same issue with the ipv6 address family not being activated
Error: Disk cannot be removed
Hi every all .
I'm running into an issue with Proxmox 9.2.3 when moving a VM to a new node; it seems the old disk is still holding onto a session on the old node. I'm using local LVM. I've tried deleting them but...
Hello forum members,
As a new member, I have a question—perhaps a silly one, I’m not sure.
I am completely new to this subject, so apologies if this is a dumb question.
I have installed Proxmox Mail Gateway; I’ve managed to get a lot done using...
You can swap the RAM with one of your known-good servers first and see if the errors follow the DIMMs. The logs make me think it's more likely a memory issue than the microcode, especially with another system using the same Nemix RAM showing...
The same syndrome and nearly the same physical address occur multiple times, so this looks more like a persistent problem with a DIMM, memory channel, socket contact, memory controller or unstable RAM configuration than a random single-bit event...
You can swap the RAM with one of your known-good servers first and see if the errors follow the DIMMs. The logs make me think it's more likely a memory issue than the microcode, especially with another system using the same Nemix RAM showing...
Why is there a Proxmox VE v8.4.19 running?
What CPU Type do you use?
So get the lshw programm with apt install lshw.
for the Asrock X470D4U you can download the English manual.
and on Page 22 you find:
So your 2666 MT/s is normal with 4x DDR4...
Me too, similar situation: an "rsync -a" syncs the timestamps of the original files first and after a short while the mtime of the file switches to the time of copy. Falling back to NFS version 4.1 on the mount fixes the problem.
I have the same problem on Proxmox 9.2.4 with kernel 7.0.14-3-pve as NFS-Server and NFS-clients running 7.x kernels.
A workarround for me is to mount the filesystem with NFS version 4.1:
mount -o vers=4.1 SERVER:/DIR /mnt
I guess it is a kernel bug.
Preface:
I just registered to share my almost week long suffering chasing imaginary hardware issues and the very simpel software bug/limitation that caused it.
A few weeks ago I used Claude.ai to cobble together a comprehensive manual to get...
hello,
glad it works for you.
just leaving this link here for others using caddy + pocketid + pve:
https://forum.proxmox.com/threads/proxmox-ui-caddy-and-reverse-proxy.83198/
cheers!
Hi,
I have only registered in order to post my solution to the problem. The working entry in my Caddy config file is as follows:
proxmox.lan {
reverse_proxy 192.168.1.200:8006 {
transport http {...
Hello,
The reason you are seeing the internal gateway IP (10.0.0.1) instead of the real public IP is usually due to Source NAT (SNAT) or Masquerading being applied on the Proxmox Host alongside the DNAT rule.
When masquerading is active for the...