✅ Have you read and understood the above guidelines?
yes
🔎 Did you run the script with verbose mode enabled?
Yes, verbose mode was enabled and the output is included below
📜 What is the name of the script you are using?
https://github.com/community-scripts/ProxmoxVE/blob/main/ct/nginxproxymanager.sh
📂 What was the exact command used to execute the script?
update
⚙️ What settings are you using?
🖥️ Which Linux distribution are you using?
Debian 13
🧱 Is this Proxmox host running arm64?
Yes
📈 Which Proxmox version are you on?
9.2
📝 Provide a clear and concise description of the issue.
Launching update from the command line in LXC ends with an error on line 219 of the script.
🔄 Steps to reproduce the issue.
launch update from command line, or the script.
❌ Paste the full error output (if available).
ERROR ON LINE 219 - CERTBOT_VER=$(/opt/certbot/bin/certbot --version 2>&1 | awk '{print $NF}')
🖼️ Additional context (optional).
As said on the title I had it fixed modifiying the script with AI help changing that line to:
if [ -f /opt/certbot/bin/certbot ]; then
CERTBOT_VER=$(/opt/certbot/bin/certbot --version 2>&1 | awk '{print $NF}' || echo "0.0.0")
elif command -v certbot &>/dev/null; then
CERTBOT_VER=$(certbot --version 2>&1 | awk '{print $NF}' || echo "0.0.0")
else
CERTBOT_VER="2.0.0"
fi
The AI explanation was:
"The error you are experiencing on that line usually occurs due to a very subtle detail: awk breaks or returns an error if the path /opt/certbot/bin/certbot does not exist or if it is executed within an environment where the variable is not processed correctly, blocking the script because of the catch_errors function (which usually has set -e enabled to stop the script upon any failure).
Even if you have certbot installed globally on your system, this specific Proxmox VE script (from the tteck community) looks for an exclusive Python virtual environment in /opt/certbot/. If that folder does not exist or is corrupted, the command fails instantly."
Indeed my certbot location its in /usr/...
This instalation comes from earlier versions of npm and debian 12.
I open this as an issue because I do not know if it's just my container problem. Maybe the solution works for me but its not good for everyone.
✅ Have you read and understood the above guidelines?
yes
🔎 Did you run the script with verbose mode enabled?
Yes, verbose mode was enabled and the output is included below
📜 What is the name of the script you are using?
https://github.com/community-scripts/ProxmoxVE/blob/main/ct/nginxproxymanager.sh
📂 What was the exact command used to execute the script?
update
⚙️ What settings are you using?
🖥️ Which Linux distribution are you using?
Debian 13
🧱 Is this Proxmox host running arm64?
Yes
📈 Which Proxmox version are you on?
9.2
📝 Provide a clear and concise description of the issue.
Launching update from the command line in LXC ends with an error on line 219 of the script.
🔄 Steps to reproduce the issue.
launch update from command line, or the script.
❌ Paste the full error output (if available).
ERROR ON LINE 219 - CERTBOT_VER=$(/opt/certbot/bin/certbot --version 2>&1 | awk '{print $NF}')
🖼️ Additional context (optional).
As said on the title I had it fixed modifiying the script with AI help changing that line to:
if [ -f /opt/certbot/bin/certbot ]; then
CERTBOT_VER=$(/opt/certbot/bin/certbot --version 2>&1 | awk '{print $NF}' || echo "0.0.0")
elif command -v certbot &>/dev/null; then
CERTBOT_VER=$(certbot --version 2>&1 | awk '{print $NF}' || echo "0.0.0")
else
CERTBOT_VER="2.0.0"
fi
The AI explanation was:
"The error you are experiencing on that line usually occurs due to a very subtle detail: awk breaks or returns an error if the path /opt/certbot/bin/certbot does not exist or if it is executed within an environment where the variable is not processed correctly, blocking the script because of the catch_errors function (which usually has set -e enabled to stop the script upon any failure).
Even if you have certbot installed globally on your system, this specific Proxmox VE script (from the tteck community) looks for an exclusive Python virtual environment in /opt/certbot/. If that folder does not exist or is corrupted, the command fails instantly."
Indeed my certbot location its in /usr/...
This instalation comes from earlier versions of npm and debian 12.
I open this as an issue because I do not know if it's just my container problem. Maybe the solution works for me but its not good for everyone.