https://blog.margrop.net/en/tag/uptimekuma/ Recent content in UptimeKuma on Margrop Blog Hugo -- gohugo.io en-US Wed, 14 May 2025 22:16:48 +0800 https://blog.margrop.net/en/post/pve-host-virtual-machine-disk-space-monitor-experience-step-two/ Wed, 14 May 2025 22:16:48 +0800 https://blog.margrop.net/en/post/pve-host-virtual-machine-disk-space-monitor-experience-step-two/ Read first The previous article showed how to push the PVE host’s LVM-Thin usage to UptimeKuma. After following the instructions, some readers got a 404 when the script used curl. This article explains the cause, fixes the script, and provides an optional upgrade path. Follow along from scratch and you should succeed on the first try. 1 Phenomenon: curl ... 404 curl -fsS --retry 3 \ "${PUSH_URL}?status=up&msg=OK" \ -H 'Content-Type: application/json' \ --data-raw "$result" # ↳ curl: (22) The requested URL returned error: 404 The same URL works in a browser or with curl GET: https://blog.margrop.net/en/post/pve-host-virtual-machine-lvm-disk-space-monitor-experience/ Wed, 14 May 2025 22:11:33 +0800 https://blog.margrop.net/en/post/pve-host-virtual-machine-lvm-disk-space-monitor-experience/ Target Reader This article is written for readers who have just started using Proxmox VE (referred to as PVE) and want to copy the steps and get it running. The article aims to: explain why the problem happens provide the full command at each step give troubleshooting ideas when something goes wrong 0 Background - What went wrong? The official PVE installation wizard defaults to putting the VM disk into the LVM-Thin pool (commonly pve/data)