惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

量子位
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
F
Fortinet All Blogs
博客园 - 聂微东
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Hugging Face - Blog
Hugging Face - Blog
V
Visual Studio Blog
小众软件
小众软件
有赞技术团队
有赞技术团队
雷峰网
雷峰网
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
AWS News Blog
AWS News Blog
C
Cisco Blogs
美团技术团队
T
Threat Research - Cisco Blogs
C
CERT Recently Published Vulnerability Notes
人人都是产品经理
人人都是产品经理
宝玉的分享
宝玉的分享
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
酷 壳 – CoolShell
酷 壳 – CoolShell
Stack Overflow Blog
Stack Overflow Blog
W
WeLiveSecurity
D
DataBreaches.Net
博客园 - 司徒正美
Blog — PlanetScale
Blog — PlanetScale
IT之家
IT之家
云风的 BLOG
云风的 BLOG
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Simon Willison's Weblog
Simon Willison's Weblog
Google DeepMind News
Google DeepMind News
T
The Blog of Author Tim Ferriss
Know Your Adversary
Know Your Adversary
NISL@THU
NISL@THU
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Vercel News
Vercel News
月光博客
月光博客
T
Tailwind CSS Blog
H
Help Net Security
aimingoo的专栏
aimingoo的专栏
P
Proofpoint News Feed
Application and Cybersecurity Blog
Application and Cybersecurity Blog
Spread Privacy
Spread Privacy
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
Cisco Talos Blog
Cisco Talos Blog
Microsoft Security Blog
Microsoft Security Blog
V
V2EX
WordPress大学
WordPress大学
Cyberwarzone
Cyberwarzone
Recent Announcements
Recent Announcements

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice ceph-osd crashes with kernel 6.17.2-1-pve on Dell system [META] Links on Proxmox Forum Website Hardwarer oder Software RAID Joining a cluster with already created guests VM PDM missing backup jobs from PVE / Log retention Remove VM.Monitor from all users/roles, PVE 9.2 Proxmox Freezing (new instalation) 9.2.2 - Intel 12700T No Web gui and random connection reset by peer [SOLVED] - i40e module for X710 Intel NIC Dutch Proxmox Day 2026 How pools use the space Corosync initiiert Reboot trotz Verfügbarkeit der Systeme Opt-in Linux 7.0 Kernel for Proxmox VE 9 available After PVE 8to9 upgrade, unable to check guest fs freeze status Problem with MegaRAID SAS3508 controller proxmox-kernel-7.0.2-6-pve failing network service Auto sync guest time after rollback of VM snapshot with RAM/state Broadcom BCM57504 (100G) bnxt_en TX timeout and NIC reset on Proxmox 8.1.5 — while BCM57414 (25G) works fine on same host QEMU 11.0 available on pve-test and pve-no-subscription as of now 350 MPM Solventless Lamination Machine for High-Speed Flexible Packaging Making sense of NVMe zfs and SMART errors [SOLVED] - PVE loses network connection after kernel upgrade to proxmox-kernel-7.0.0-3-pve [SOLVED] - Remove or reset cluster configuration. Proxmox 8.4.1 Fresh Install BCM57416 10G Ethernet Adapter Not Recognized PDM 1.1.1 unable to add AD realm with anonymous search [TUTORIAL] - Developer Workstation (Proxmox-VE 9) with cinnamon (LMDE7) SDN zone shows "pending" on peer nodes after node reboot (9.2.x) Cluster not quorate - extending auth key lifetime! Proxmox not rebooting properly (SOLVED) Proxmox 9 Stuck on loading initial ramdisk With new HA-Disarm Feature is there a Documentation for NUT Setup on Clusters? Proxmox 8.3 Installation Issue on ProLiant DL380 Gen9 Cluster networking setup LXC System images unavailable [SOLVED] - Fix: NVIDIA Drivers Failing after upgrade to Proxmox 9.2.2 (Kernel 7.0.2-6-pve) / NovaCore Conflict Install NUT directly on Proxmox VE and control guests from here driver usb for windows 7 System startup error and no network: Failed to start ifupdown2-pre.service - Helper to synchronize boot up for ifupdown. PBS backup space grow up constantly Proxmox Datacenter Manager 1.1 released! IPv4 not available in newly created VM Recommended Setup for Offsite Proxmox Backups? Hetzner Storage Box & Remote PBS Challenges duplicate, please delete this passthrought an USB device "by ID" to CT PDM Installer Freezes at 66% Tried PDM for the first time (version 1.1) - had issues PDM 1.1 automated install Suche Server-Provider für Proxmox connecting sdn to edge firewall SDN, IPAM & DHCP Migrating from read-only file system Ubuntu 26.04 installation fails for unknown reason Status Unbekannt nach Cluster Join Installing Proxmox Backup Server on Mac Mini (Late 2012) kernel 7.0 performance issue with zfs pools PVE becomes unreachable via ethernet but OS is running [SOLVED] - New 9.2 install - can't find 7.0.2-6-pve , not all the time [SOLVED] - Backup and dedupe a VM with LUKS Gibt es mit PVE 2.x ggf. Änderungen bei der RAM-Nutzung, bzw. deren Anzeige bei VMs? I need help for setting up backup solution Way more NAGware, very little functionality, bugs galore Root squashing virtiofsd with --uid-map Intel ixgbe Driver Update Fail Passkey Login (not 2FA) Roblox VM detection - can be overcome? [TUTORIAL] - ZFS-Autosnaptshot inkl. Rollback und Daten direkt recovern (Windows/Linux) How to stop PVE Kernel upgrade [SOLVED] - very long waiting to log in to lxc debian 11 ssh [TUTORIAL] - Configuring Fusion-Io (SanDisk) ioDrive, ioDrive2, ioScale and ioScale2 cards with Proxmox Increase maximum USB devices in vm.conf
Wake on lan for VM
invalid@exam · 2026-06-26 · via Proxmox Support Forum

Hello,

Some VMs are only useful on demand. Leaving them running all the time is a waste of hardware capacity.

I would like to allow users to run them on demand.

There are two solutions to do this:

1/ go through GUI permissions management.

But, to have VM.PowerMgmt rights, VM.Audit must also be allowed. The latter gives access to the notes of the summary, which may have content that should not be distributed.

> Is there a way to give only VM.PowerMgmt rights on certain VMs, without any other rights?

2/ use the Wake on lan command for VMs.

But VM bios do not include Wol function.

> How to do it?

Could you enhance the GUI to allow Wol on VMs?

Best regards

Hello

Wake on Lan needs a network card connected that in fact is powered.
As the VM does not really exist, for simulating this, the VM shoud be powered but in a "low powered" mode to only respond on a WOL packet ... I'm not sure that this functionnality would be power efficient regarding the normal electrical power consumption of a VM that does nothing.

A possible way is to script the "start" of the VM thru the Proxmox API.
https://pve.proxmox.com/wiki/Proxmox_VE_API

Regards

Hello Pierre-Yves,

Thank you for your answer.

It's not a question of energy, but rather of memory and processor resources. There are also many other reasons not to let machines run unnecessarily, if only in terms of security.
I am well aware of how WOL works. But since VM network cards are vitruous, I suppose that the magic packet addressed to their mac address can be "listened to" at the node, which will trigger their boot.

I've seen the API an script way, but don't have the level.
Best regards

To the OP did you ever figure this out? I remember having this functionality enabled in esxi when using a win10/gpu for a htpc function. At the end of the session the windows vm would be put to 'sleep', then wake via wol (shortcut on cell phone or any other standard wol magic packet) next time.

To the OP did you ever figure this out? I remember having this functionality enabled in esxi when using a win10/gpu for a htpc function. At the end of the session the windows vm would be put to 'sleep', then wake via wol (shortcut on cell phone or any other standard wol magic packet) next time.

No, and apparently there is little demand to integrate this function.
If this exists in other virtualization software, maybe the Proxmox team could take up the subject...
Thanks for your contribution

I wonder why it seems that nobody had the idea to do a search for this topic. Even "the search engine" finds this tagged old thread:
https://forum.proxmox.com/threads/update-wake-and-other-on-lan-for-vms-v0-3.26381/

Thank you for your contribution.
It seems that you are more efficient than me in your research.
This post had escaped me, and is indeed very interesting.
Anyway, since this feature exists in competing supervisors, maybe the Proxmox team could add the development of this feature into their roadmap, especially since you have done all the work to facilitate this...
I am not a computer scientist, and not very comfortable with scripts. So it would be easier for me if this function was built into the GUI.
If someone from the Proxmox team could take a stand, it would be nice.

Last edited:

The feature should be part of the proxmox services. So that any client, e.g. miniWOL can power up any VM as long as proxmox itself is running. Maybe the service written by @ojaksch can be made a default setup of proxmox.

(To get proxmox running, this setting can be enabled in the BIOS or by setting the network card via the console (and setting up a service that does it after every boot).)

Hello,
i fixed that with that simple Script:

Bash:

#!/bin/bash
re='^[0-9]+$'
while true ; do
    echo "\n" | nc -knl -p 9 -u | # listen to udp port 9 for packets, check if it is a magic packet
        stdbuf -o0 xxd -c 6 -p |
        stdbuf -o0 uniq |
        stdbuf -o0 grep -v 'ffffffffffff' |
        while read ; do
            macWOL="${REPLY:0:2}:${REPLY:2:2}:${REPLY:4:2}:${REPLY:6:2}:${REPLY:8:2}:${REPLY:10:2}"
            macWOL=`echo "$macWOL" |tr "[:upper:]" "[:lower:]"`     
            /usr/sbin/qm list  |tr -s ' ' | cut -d ' ' -f 2 | while read -r id ; do
            if [[ $id =~ $re ]] ; then
                echo  "check VM-ID $id for $macWOL"
                /usr/sbin/qm config $id | grep ^net0 | while read -r macstr ; do
                    macstr=`echo "$macstr" |tr "[:upper:]" "[:lower:]"`
                    if [[ $macstr == *"$macWOL"* ]]; then
                        echo "MAC $macWOL found at VMID  $id. Starting VM"
                        /usr/sbin/qm start $id
                    fi
                done
            fi
        done
    done
done

This script evaluates the magic packet on the proxmox host and checks wich VMS have the MAC-Address provided by the Magic Packet. Then the VM with the correct MAC-Address ist started.

Hi @stele99
works well thank you!
If so else needs it: I took your script, made it executable and startet it. Will be scheduled with cron in future.
I had the problem that the WOL package was not received by the script - I then noticed that the WOL tool (WOL2) by default uses port 6 instead of 9.

BR,
Hugo

Considering this discussion, I found it easier to use Proxmox API.
I created an API token for my user followed by its permission.
Then saved the token to a file in my user's home and restricted its permissions.

The following script works for me.

Bash:

#!/bin/bash

# SCRIPT TO START A PROXMOX VM

# SET UP API
PROX_HOST="proxmox.domain"
PROX_HOST_PORT="8006"
APIURL="https://${PROX_HOST}:${PROX_HOST_PORT}/api2"


# SET UP USER
TOKEN_FILE="./.pve-token"
TOKEN_NAME="API"
USERNAME="username"
REALM="pve"


# SET UP VM
NODE_NAME="node"
VM_TYPE="qemu"          # "qemu" for VM or "lxc" for container
VMID="106"


# POST A START REQUEST
curl -k -X POST \
        -H "Authorization: PVEAPIToken=${USERNAME}@${REALM}!${TOKEN_NAME}=$(cat $TOKEN_FILE)" \
        ${APIURL}/json/nodes/${NODE_NAME}/${VM_TYPE}/${VMID}/status/start

Observe the variables values for your own environment.

Last edited:

I been searching for this solution for a long time, I end up using ssh Snippets eg “qm start 100”

Last edited:

I been searching for this solution for a long time, I end up using ssh Snippets eg “qm start 100”

kindly explain how exactly are you doing it?

kindly explain how exactly are you doing it?

I use an app call Termius. Add proxmox as host. Add “qm start xxx” in Snippets. Everytime you want to start the vm open app, press the snippets.

@stele99 and others with an idea,
first of all thank you for your elegant short script. The first access to a switched off desired VM works perfectly. But as soon as I shut down the awakened VM and want to control it again, your script no longer registers the WOL packets. Sometimes it works twice but at the latest the third time it doesn't work anymore.
It never works with access to another following inactive VM.
Unfortunately, I can't see any causal error in your script. Do you have an idea?
If I abort the script and start it again, it works immediately as desired. The connection is made via Guacamole, for which WOL can be activated in the connection settings.

tcpdump -v -i vmbr0 ether proto 0x0842 or udp port 9
shows always received WOL-packets.

Last edited:

After trying to narrow down the problem for a few days, I ended up with the following condensed script:
#!/bin/bash while true ; do # listen to udp port 9 for packets, check if it is a magic packet echo "\n" | nc -knl -p 9 -u done
This stops working for me after about 5 attempts.
So it seems to be due to Netcat. Wrong parameter problem? Internal netcat problem?
Does anyone have an idea?

Last edited:

Hello,
i fixed that with that simple Script:

Bash:

#!/bin/bash
re='^[0-9]+$'
while true ; do
    echo "\n" | nc -knl -p 9 -u | # listen to udp port 9 for packets, check if it is a magic packet
        stdbuf -o0 xxd -c 6 -p |
        stdbuf -o0 uniq |
        stdbuf -o0 grep -v 'ffffffffffff' |
        while read ; do
            macWOL="${REPLY:0:2}:${REPLY:2:2}:${REPLY:4:2}:${REPLY:6:2}:${REPLY:8:2}:${REPLY:10:2}"
            macWOL=`echo "$macWOL" |tr "[:upper:]" "[:lower:]"` 
            /usr/sbin/qm list  |tr -s ' ' | cut -d ' ' -f 2 | while read -r id ; do
            if [[ $id =~ $re ]] ; then
                echo  "check VM-ID $id for $macWOL"
                /usr/sbin/qm config $id | grep ^net0 | while read -r macstr ; do
                    macstr=`echo "$macstr" |tr "[:upper:]" "[:lower:]"`
                    if [[ $macstr == *"$macWOL"* ]]; then
                        echo "MAC $macWOL found at VMID  $id. Starting VM"
                        /usr/sbin/qm start $id
                    fi
                done
            fi
        done
    done
done

This script evaluates the magic packet on the proxmox host and checks wich VMS have the MAC-Address provided by the Magic Packet. Then the VM with the correct MAC-Address ist started.

Hello,
I change script stele99 and now this start WOL your CT too:

wol.sh

Bash:

#!/bin/bash
re='^[0-9]+$'
while true ; do
    echo "\n" | nc -knl -p 9 -u | # listen to udp port 9 for packets, check if it is a magic packet
        stdbuf -o0 xxd -c 6 -p |
        stdbuf -o0 uniq |
        stdbuf -o0 grep -v 'ffffffffffff' |
        while read ; do
            macWOL="${REPLY:0:2}:${REPLY:2:2}:${REPLY:4:2}:${REPLY:6:2}:${REPLY:8:2}:${REPLY:10:2}"
            macWOL=`echo "$macWOL" |tr "[:upper:]" "[:lower:]"`  
            /usr/sbin/qm list  |tr -s ' ' | cut -d ' ' -f 2 | while read -r id ; do
            if [[ $id =~ $re ]] ; then
                echo  "check VM-ID $id for $macWOL"
                /usr/sbin/qm config $id | grep ^net0 | while read -r macstr ; do
                    macstr=`echo "$macstr" |tr "[:upper:]" "[:lower:]"`
                    if [[ $macstr == *"$macWOL"* ]]; then
                        echo "MAC $macWOL found at VMID  $id. Starting VM"
                        /usr/sbin/qm start $id
                    fi
                done
            fi
    done
        /usr/sbin/pct list  |tr -s ' ' | cut -d ' ' -f 1 | while read -r id ; do
            if [[ $id =~ $re ]] ; then
                echo  "check VM-ID $id for $macWOL"
                /usr/sbin/pct config $id | grep ^net0 | while read -r macstr ; do
                    macstr=`echo "$macstr" |tr "[:upper:]" "[:lower:]"`
                    if [[ $macstr == *"$macWOL"* ]]; then
                        echo "MAC $macWOL found at VMID  $id. Starting VM"
                        /usr/sbin/pct start $id
                    fi
                done
            fi
        done
    done
done

And add to autostart:

cp wol.sh /usr/local/bin/wol.sh
chmod +x /usr/local/bin/wol.sh

make file wol.service.app

Code:

[Unit]
Description=WOL (Wakeup on LAN)

[Service]
Type=simple
ExecStart=/bin/bash /usr/local/bin/wol.sh

[Install]
WantedBy=multi-user.target

cp wol.service.app /etc/systemd/system/wol.service
chmod 644 /etc/systemd/system/wol.service
systemctl enable wol.service

reboot your server and try

Last edited:

Did you see/checked any difference between systemd-autostart and manual shell-start regarding my comments?

Hello,
I change script stele99 and now this start WOL your CT too:

wol.sh

Bash:

#!/bin/bash
re='^[0-9]+$'
while true ; do
    echo "\n" | nc -knl -p 9 -u | # listen to udp port 9 for packets, check if it is a magic packet
        stdbuf -o0 xxd -c 6 -p |
        stdbuf -o0 uniq |
        stdbuf -o0 grep -v 'ffffffffffff' |
        while read ; do
            macWOL="${REPLY:0:2}:${REPLY:2:2}:${REPLY:4:2}:${REPLY:6:2}:${REPLY:8:2}:${REPLY:10:2}"
            macWOL=`echo "$macWOL" |tr "[:upper:]" "[:lower:]"`
            /usr/sbin/qm list  |tr -s ' ' | cut -d ' ' -f 2 | while read -r id ; do
            if [[ $id =~ $re ]] ; then
                echo  "check VM-ID $id for $macWOL"
                /usr/sbin/qm config $id | grep ^net0 | while read -r macstr ; do
                    macstr=`echo "$macstr" |tr "[:upper:]" "[:lower:]"`
                    if [[ $macstr == *"$macWOL"* ]]; then
                        echo "MAC $macWOL found at VMID  $id. Starting VM"
                        /usr/sbin/qm start $id
                    fi
                done
            fi
    done
        /usr/sbin/pct list  |tr -s ' ' | cut -d ' ' -f 1 | while read -r id ; do
            if [[ $id =~ $re ]] ; then
                echo  "check VM-ID $id for $macWOL"
                /usr/sbin/pct config $id | grep ^net0 | while read -r macstr ; do
                    macstr=`echo "$macstr" |tr "[:upper:]" "[:lower:]"`
                    if [[ $macstr == *"$macWOL"* ]]; then
                        echo "MAC $macWOL found at VMID  $id. Starting VM"
                        /usr/sbin/pct start $id
                    fi
                done
            fi
        done
    done
done

And add to autostart:

cp wol.sh /usr/local/bin/wol.sh
chmod +x /usr/local/bin/wol.sh

make file wol.service.app

Code:

[Unit]
Description=WOL (Wakeup on LAN)

[Service]
Type=simple
ExecStart=/bin/bash /usr/local/bin/wol.sh

[Install]
WantedBy=multi-user.target

cp wol.service.app /etc/systemd/system/wol.service
chmod 644 /etc/systemd/system/wol.service
systemctl enable wol.service

reboot your server and try

This script still seems to stop after the first received magic package.. I'm not 100% sure what exactly is happening, but from some troubleshooting I can now tell:

  1. Script receives magic package containing the MAC address to be woken up
  2. Script goes through one iteration for every VM and container, eventually waking up the desired one
  3. Script goes through an additional iteration within

Bash:

echo "\n" | nc -knl -p 9 -u | # listen to udp port 9 for packets, check if it is a magic packet
        stdbuf -o0 xxd -c 6 -p |
        stdbuf -o0 uniq |
        stdbuf -o0 grep -v 'ffffffffffff' |
        while read ; do

with the MAC-address being set to 00:00:00:00:00:00​

4. Script hangs in an infinite loop, never listening to another magic package​

Here is my dirty fix, which

  • just restarts the service in order to reset the script*
  • added some extra logging for journalctl -u wol.service -f
  • adds "resume" to the wake-up call, if the machine is sleeping

*(I chose this way instead of calling the script again, since that would probably cause memory issues for longer operation – anybody feel free to correct me; I'm new to this)

I tried to figure out how to break or continue the while read loop, but I wasn't able to.. If someone knows bash a bit better than me, please provide your solution since that would be much cleaner than restarting the service..

Bash:

#!/bin/bash
re='^[0-9]+$'
port=7 # Define UDP port to listen on for the package
echo "Starting Wake on LAN script"

while true ; do
    echo "Listening on UDP port $port ..."
    echo "\n" | nc -knl -p $port -u | # listen to udp port (default: 9) for packets, check if it is a magic packet
        stdbuf -o0 xxd -c 6 -p |
        stdbuf -o0 uniq |
        stdbuf -o0 grep -v 'ffffffffffff' |
    while read ; do
        macWOL="${REPLY:0:2}:${REPLY:2:2}:${REPLY:4:2}:${REPLY:6:2}:${REPLY:8:2}:${REPLY:10:2}"
          if [[ "00:00:00:00:00:00" == *"$macWOL"* ]]; then
            echo "script is finished and would go to endless loop. Restarting service..."
            systemctl restart wol.service
          fi
        macWOL=`echo "$macWOL" |tr "[:upper:]" "[:lower:]"`
        #VM loop
            /usr/sbin/qm list  |tr -s ' ' | cut -d ' ' -f 2 | while read -r id ; do
            if [[ $id =~ $re ]] ; then
                echo  "check VM-ID $id for $macWOL"
                /usr/sbin/qm config $id | grep ^net0 | while read -r macstr ; do
                    macstr=`echo "$macstr" |tr "[:upper:]" "[:lower:]"`
                    if [[ $macstr == *"$macWOL"* ]]; then
                        echo "MAC $macWOL found at VMID  $id. Starting VM"
                        /usr/sbin/qm start $id
                        /usr/sbin/qm resume $id
                    fi
                done
            fi
    done
  
        #container loop
        /usr/sbin/pct list  |tr -s ' ' | cut -d ' ' -f 1 | while read -r id ; do
            if [[ $id =~ $re ]] ; then
                echo  "check VM-ID $id for $macWOL"
                /usr/sbin/pct config $id | grep ^net0 | while read -r macstr ; do
                    macstr=`echo "$macstr" |tr "[:upper:]" "[:lower:]"`
                    if [[ $macstr == *"$macWOL"* ]]; then
                        echo "MAC $macWOL found at VMID  $id. Starting VM"
                        /usr/sbin/pct start $id
                        /usr/sbin/pct resume $id
                    fi
                done
            fi
        done
    done
# the script never reaches here.. and I do not know why,
# which is why we just restart the service to listen for
# new magic packages after the first iteration
done

echo "script has concluded and stopped.. this should never happen"

Last edited:

I keep getting this error: stdbuf: failed to run command ‘xxd’: No such file or directory

Idk if it's because I'm using PVE 8.0.3, but I would like to use this script for my config.