SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-03 04:32:27 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Scripts failing on "Create LXC Container" when setting a root password or CTID #1474

New Issue
Closed
opened 2025-11-20 05:11:01 -05:00 by saavagebueno · 11 comments
saavagebueno commented 2025-11-20 05:11:01 -05:00
Owner
Copy Link

Originally created by @reichbc on GitHub (Jul 12, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

ntfy, netbox

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/ntfy.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Starting about a week ago, every helper script I attempt to run with Advanced Settings has failed at the "Create LXC Container" step with an unspecified error when setting the Root Password or CTID;

[ERROR] in line 1095: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $?

This happens no matter what combination of other settings I use. Originally I assumed it was because my preferred password contains a $, but switching to plain a-z 0-9 does not solve it.

I specifically use Advanced Options because the Default Settings option does not allow me to select the CTID, which is critical for my own organizational process. I wouldn't mind using the default options if at least the CTID was editable.

I did test with Default Settings, it works just fine, but then I have to go through the manual steps to change the CTID myself along with the associated disk and other metadata information.

Testing Advanced Settings with no option changes (just slamming enter till it goes) does succeed.

Running the script in Verbose Mode produces no meaningful output, so I do not know how else to provide exactly what's causing this crash.

Possibly related to #5930 where the message is "Password cannot be empty" if settings are saved to a config file and replayed.

🔄 Steps to reproduce the issue.

  1. Run script in Advanced Settings mode. Settings other than Root Password or CTID don't seem to matter.
  2. Observe error.

❌ Paste the full error output (if available).

          __  ____     
   ____  / /_/ __/_  __
  / __ \/ __/ /_/ / / /
 / / / / /_/ __/ /_/ / 
/_/ /_/\__/_/  \__, /  
              /____/   
  🧩  Using Advanced Settings on node P3
  🖥️  Operating System: debian
  🌟  Version: 12
  📦  Container Type: Unprivileged
  🔐  Root Password: ********
  🆔  Container ID: 102
  🏠  Hostname: ntfy
  💾  Disk Size: 2 GB
  🧠  CPU Cores: 1
  🛠️  RAM Size: 512 MiB
  🌉  Bridge: vmbr0
  📡  IPv4: DHCP
  📡  IPv6: Disabled
  📡  APT-Cacher IP Address: Default
  ⚙️  Interface MTU Size: Default
  🔍  DNS Search Domain: Host
  📡  DNS Server IP Address: Host
  🏷️  Vlan: Default
  📡  Tags: community-script;notification
  🔑  Root SSH Access: no
  🗂️  Enable FUSE Support: no
  🔍  Verbose Mode: no
  🚀  Creating a ntfy LXC using the above advanced settings
  ✔️   Validated Storage (rootdir / vztmpl).
  ✔️   Cluster is quorate
  ✔️   LXC Template List Updated
⠸ Creating LXC Container
[ERROR] in line 1095: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $?

🖼️ Additional context (optional).

No response

Originally created by @reichbc on GitHub (Jul 12, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? ntfy, netbox ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/ntfy.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Starting about a week ago, every helper script I attempt to run with Advanced Settings has failed at the "Create LXC Container" step with an unspecified error when setting the Root Password or CTID; ```[ERROR] in line 1095: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $?``` This happens no matter what combination of other settings I use. Originally I assumed it was because my preferred password contains a `$`, but switching to plain a-z 0-9 does not solve it. I specifically use Advanced Options because the Default Settings option does not allow me to select the CTID, which is critical for my own organizational process. I wouldn't mind using the default options if at least the CTID was editable. I did test with Default Settings, it works just fine, but then I have to go through the manual steps to change the CTID myself along with the associated disk and other metadata information. Testing Advanced Settings with no option changes (just slamming enter till it goes) does succeed. Running the script in Verbose Mode produces no meaningful output, so I do not know how else to provide exactly what's causing this crash. Possibly related to #5930 where the message is "Password cannot be empty" if settings are saved to a config file and replayed. ### 🔄 Steps to reproduce the issue. 1. Run script in Advanced Settings mode. Settings other than Root Password or CTID don't seem to matter. 2. Observe error. ### ❌ Paste the full error output (if available). ``` __ ____ ____ / /_/ __/_ __ / __ \/ __/ /_/ / / / / / / / /_/ __/ /_/ / /_/ /_/\__/_/ \__, / /____/ 🧩 Using Advanced Settings on node P3 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 102 🏠 Hostname: ntfy 💾 Disk Size: 2 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 512 MiB 🌉 Bridge: vmbr0 📡 IPv4: DHCP 📡 IPv6: Disabled 📡 APT-Cacher IP Address: Default ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;notification 🔑 Root SSH Access: no 🗂️ Enable FUSE Support: no 🔍 Verbose Mode: no 🚀 Creating a ntfy LXC using the above advanced settings ✔️ Validated Storage (rootdir / vztmpl). ✔️ Cluster is quorate ✔️ LXC Template List Updated ⠸ Creating LXC Container [ERROR] in line 1095: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $? ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the not a script issue label 2025-11-20 05:11:01 -05:00
saavagebueno commented 2025-11-20 05:11:02 -05:00
Author
Owner
Copy Link

@reichbc commented on GitHub (Jul 12, 2025):

Updated the title as it appears to be more than just the root password setting.

Trying again with the following conditions;

  • modifying only the root password: fail
  • modifying only the CTID, nothing else: fail
  • modifying only the hostname: pass
  • modifying only the disk size: pass
  • modifying only CPU core count: pass
  • modifying only memory size: pass
  • adding a search domain: pass

Creating a brand new full container changing all of the settings above that pass and none that fail: pass.

So, looks like modifying root password and CTID are killing the scripts.

@reichbc commented on GitHub (Jul 12, 2025): Updated the title as it appears to be more than just the root password setting. Trying again with the following conditions; - modifying only the root password: fail - modifying only the CTID, nothing else: fail - modifying only the hostname: pass - modifying only the disk size: pass - modifying only CPU core count: pass - modifying only memory size: pass - adding a search domain: pass Creating a brand new full container changing all of the settings above that `pass` and none that `fail`: pass. So, looks like modifying root password and CTID are killing the scripts.
saavagebueno commented 2025-11-20 05:11:02 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 12, 2025):

@community-scripts/contributor can anyone Approve this?

@MickLesk commented on GitHub (Jul 12, 2025): @community-scripts/contributor can anyone Approve this?
saavagebueno commented 2025-11-20 05:11:02 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jul 12, 2025):

cant reproduce the issue:
advanced mode, ctid set, root pass set

Image
@tremor021 commented on GitHub (Jul 12, 2025): cant reproduce the issue: advanced mode, ctid set, root pass set <img width="880" height="785" alt="Image" src="https://github.com/user-attachments/assets/9e1ca1db-87da-4ad9-ba81-fcb09cadf2de" />
saavagebueno commented 2025-11-20 05:11:02 -05:00
Author
Owner
Copy Link

@endavis commented on GitHub (Jul 13, 2025):

I am seeing the same issue when trying to install proxmox backup server with the command "bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/proxmox-backup-server.sh)" andn using advanced install.

Edit: Default settings work except I need to add a vlan id so the update errors out because it can't download the packages.

🧩 Using Advanced Settings on node pve1
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: Automatic Login
🆔 Container ID: 112
🏠 Hostname: proxmox-backup-server
💾 Disk Size: 10 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🌉 Bridge: vmbr0
📡 IPv4: DHCP
📡 IPv6: SLAAC/AUTO
📡 APT-Cacher IP Address: Default
⚙️ Interface MTU Size: 9000
🔍 DNS Search Domain: xxxxx.net
📡 DNS Server IP Address: Host
🏷️ Vlan: 2
📡 Tags: community-script;backup
🔑 Root SSH Access: no
🗂️ Enable FUSE Support: yes
🔍 Verbose Mode: yes
🚀 Creating a Proxmox-Backup-Server LXC using the above advanced settings
✔️ Validated Storage (rootdir / vztmpl).
✔️ Cluster is quorate
✔️ LXC Template List Updated
⏳ Creating LXC Container
[ERROR] in line 1095: exit code 0: while executing command bash -c "(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" ?

@endavis commented on GitHub (Jul 13, 2025): I am seeing the same issue when trying to install proxmox backup server with the command "bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/proxmox-backup-server.sh)" andn using advanced install. Edit: Default settings work except I need to add a vlan id so the update errors out because it can't download the packages. 🧩 Using Advanced Settings on node pve1 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: Automatic Login 🆔 Container ID: 112 🏠 Hostname: proxmox-backup-server 💾 Disk Size: 10 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🌉 Bridge: vmbr0 📡 IPv4: DHCP 📡 IPv6: SLAAC/AUTO 📡 APT-Cacher IP Address: Default ⚙️ Interface MTU Size: 9000 🔍 DNS Search Domain: xxxxx.net 📡 DNS Server IP Address: Host 🏷️ Vlan: 2 📡 Tags: community-script;backup 🔑 Root SSH Access: no 🗂️ Enable FUSE Support: yes 🔍 Verbose Mode: yes 🚀 Creating a Proxmox-Backup-Server LXC using the above advanced settings ✔️ Validated Storage (rootdir / vztmpl). ✔️ Cluster is quorate ✔️ LXC Template List Updated ⏳ Creating LXC Container [ERROR] in line 1095: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $?
saavagebueno commented 2025-11-20 05:11:03 -05:00
Author
Owner
Copy Link

@liubsp commented on GitHub (Jul 13, 2025):

I also observe this error. I use docker.sh script with default config.

⚙️ Using Default Settings on node moon
🆔 Container ID: 105
🖥️ Operating System: debian (12)
📦 Container Type: Unprivileged
💾 Disk Size: 4 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🚀 Creating a Docker LXC using the above default settings

✔️ Validated Storage (rootdir / vztmpl).
✔️ LXC Template List Updated
⠧ Creating LXC Container
[ERROR] in line 1095: exit code 0: while executing command bash -c "(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" ?

From Proxmox:

mounting container failed

TASK ERROR: unable to create CT 105 - cannot open directory //rpool/data: No such file or directory

Note that my ZFS dataset for containers is rpool/data/containers which is mounted at /zfs/local/containers. I have fixed this error by changing the mount point from /zfs/local/containers to /rpool/data/containers. Also, there were a few other errors which I have fixed after looking into Task log at Proxmox Web UI.

@liubsp commented on GitHub (Jul 13, 2025): I also observe this error. I use docker.sh script with default config. ⚙️ Using Default Settings on node moon 🆔 Container ID: 105 🖥️ Operating System: debian (12) 📦 Container Type: Unprivileged 💾 Disk Size: 4 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🚀 Creating a Docker LXC using the above default settings ✔️ Validated Storage (rootdir / vztmpl). ✔️ LXC Template List Updated ⠧ Creating LXC Container [ERROR] in line 1095: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $? From Proxmox: > mounting container failed > > TASK ERROR: unable to create CT 105 - cannot open directory //rpool/data: No such file or directory Note that my ZFS dataset for containers is `rpool/data/containers` which is mounted at `/zfs/local/containers`. I have fixed this error by changing the mount point from `/zfs/local/containers` to `/rpool/data/containers`. Also, there were a few other errors which I have fixed after looking into Task log at Proxmox Web UI.
saavagebueno commented 2025-11-20 05:11:03 -05:00
Author
Owner
Copy Link

@erdaltoprak commented on GitHub (Jul 13, 2025):

Same thing

 🧩  Using Advanced Settings on node proxmox
  🖥️  Operating System: debian
  🌟  Version: 12
  📦  Container Type: Unprivileged
  🔐  Root Password: 
  🆔  Container ID: 101
  🏠  Hostname: wireguard
  💾  Disk Size: 4 GB
  🧠  CPU Cores: 2
  🛠️  RAM Size: 1024 MiB
  🌉  Bridge: vmbr0
  📡  IPv4: DHCP
  📡  IPv6: SLAAC/AUTO
  📡  APT-Cacher IP Address: Default
  ⚙️  Interface MTU Size: Default
  🔍  DNS Search Domain: Host
  📡  DNS Server IP Address: Host
  🏷️  Vlan: Default
  📡  Tags: lxc
  🔑  Root SSH Access: no
  🗂️  Enable FUSE Support: no
  🔍  Verbose Mode: no
  🚀  Creating a Debian LXC using the above advanced settings
  💡  Configuration file already exists at /opt/community-scripts/debian.conf
  💡  Writing configuration to /opt/community-scripts/debian.conf
  ✔️   Validated Storage (rootdir / vztmpl).
  ✔️   LXC Template List Updated
⠴ Creating LXC Container
[ERROR] in line 1095: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $?

I fix it by changing the container id and deleting /opt/community-scripts unused files

@erdaltoprak commented on GitHub (Jul 13, 2025): Same thing ```sh 🧩 Using Advanced Settings on node proxmox 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: 🆔 Container ID: 101 🏠 Hostname: wireguard 💾 Disk Size: 4 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 1024 MiB 🌉 Bridge: vmbr0 📡 IPv4: DHCP 📡 IPv6: SLAAC/AUTO 📡 APT-Cacher IP Address: Default ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: lxc 🔑 Root SSH Access: no 🗂️ Enable FUSE Support: no 🔍 Verbose Mode: no 🚀 Creating a Debian LXC using the above advanced settings 💡 Configuration file already exists at /opt/community-scripts/debian.conf 💡 Writing configuration to /opt/community-scripts/debian.conf ✔️ Validated Storage (rootdir / vztmpl). ✔️ LXC Template List Updated ⠴ Creating LXC Container [ERROR] in line 1095: exit code 0: while executing command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/create_lxc.sh)" $? ``` I fix it by changing the container id and deleting `/opt/community-scripts` unused files
saavagebueno commented 2025-11-20 05:11:03 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 13, 2025):

Cant reproduce. Working fine. Alpine, Debian, Ubuntu. Tested 10 different Scripts.

Without any verbose output we cant Help.

Maybe 1-2 different screencasts are nice too

@MickLesk commented on GitHub (Jul 13, 2025): Cant reproduce. Working fine. Alpine, Debian, Ubuntu. Tested 10 different Scripts. Without any verbose output we cant Help. Maybe 1-2 different screencasts are nice too
saavagebueno commented 2025-11-20 05:11:03 -05:00
Author
Owner
Copy Link

@zster9000 commented on GitHub (Jul 14, 2025):

I was having the same issue with the linkwarden script just now. After the script failed a few times and verbose mode revealed no other info, I updated my PVE to 8.4.1 and was able to run the script successfully.

@zster9000 commented on GitHub (Jul 14, 2025): I was having the same issue with the linkwarden script just now. After the script failed a few times and verbose mode revealed no other info, I updated my PVE to 8.4.1 and was able to run the script successfully.
saavagebueno commented 2025-11-20 05:11:03 -05:00
Author
Owner
Copy Link

@endavis commented on GitHub (Jul 14, 2025):

Ok, I made some progress when installing proxmox backup server. I am on 8.4.1.

Failure with VERBOSE logging

+ [[  -features keyctl=1,nesting=1,fuse=1 -hostname proxmox-backup-server -tags community-script;backup -searchdomain=some.net -nameserver=192.168.20.1 -net0 name=eth0,bridge=vmbr0,ip=dhcpnone,tag=20,mtu=9000,ip6=auto -onboot 1 -cores 2 -memory 2048 -unprivileged 1 -password somepassword  =~  -rootfs  ]]
+ PCT_OPTIONS+=(-rootfs "$CONTAINER_STORAGE:${PCT_DISK_SIZE:-8}")
+ lockfile=/tmp/template.debian-12-standard_12.7-1_amd64.tar.zst.lock
+ exec

[ERROR] in line 1095: exit code 0: while executing command bash -c /root/test/create_lxc.sh $?

It seems that the issue in my environment involves creating the lock file with an advanced configuration. In create_lxc.sh, if the lock file exec line was piped to /dev/null if failed and never got to the point of creating the container. If I changed it to not pipe to /dev/null it worked, and the container was created.

root@pve1:~/test# diff create_lxc_orig.sh create_lxc.sh 
9c9
< # if [ "$VERBOSE" == "yes" ]; then set -x; fi
---
> if [ "$VERBOSE" == "yes" ]; then set -x; fi
312c312,313
< exec 9>"$lockfile" >/dev/null 2>&1 || {
---
> #exec 9>"$lockfile" >/dev/null 2>&1 || {
> exec 9>"$lockfile" || {

It worked without any changes to create_lxc.sh if I only used defaults to create the proxmox backup server. This doesn't work for me since I need to add a vlan. There are some other issues when using a configuration file, but I will open another issue for that.

I attached the two relevant logs.
proxmox-backup-server-success.txt
proxmox-backups-server-failed.txt

btw, debugging this is not easy. I had to download build.func, create_lxc.sh, and proxmox-backup-server.sh locally and then update the various imports of those files to use the local copy. I also had to uncomment the VERBOSE setting in create_lxc.sh. I could have at least figured out where the problem was if the VERBOSE setting was used in create_lxc.sh. I still would have had to download things locally to figure out the fix.

@endavis commented on GitHub (Jul 14, 2025): Ok, I made some progress when installing proxmox backup server. I am on 8.4.1. Failure with VERBOSE logging ``` + [[ -features keyctl=1,nesting=1,fuse=1 -hostname proxmox-backup-server -tags community-script;backup -searchdomain=some.net -nameserver=192.168.20.1 -net0 name=eth0,bridge=vmbr0,ip=dhcpnone,tag=20,mtu=9000,ip6=auto -onboot 1 -cores 2 -memory 2048 -unprivileged 1 -password somepassword =~ -rootfs ]] + PCT_OPTIONS+=(-rootfs "$CONTAINER_STORAGE:${PCT_DISK_SIZE:-8}") + lockfile=/tmp/template.debian-12-standard_12.7-1_amd64.tar.zst.lock + exec [ERROR] in line 1095: exit code 0: while executing command bash -c /root/test/create_lxc.sh $? ``` It seems that the issue in my environment involves creating the lock file with an advanced configuration. In create_lxc.sh, if the lock file exec line was piped to /dev/null if failed and never got to the point of creating the container. If I changed it to not pipe to /dev/null it worked, and the container was created. ``` root@pve1:~/test# diff create_lxc_orig.sh create_lxc.sh 9c9 < # if [ "$VERBOSE" == "yes" ]; then set -x; fi --- > if [ "$VERBOSE" == "yes" ]; then set -x; fi 312c312,313 < exec 9>"$lockfile" >/dev/null 2>&1 || { --- > #exec 9>"$lockfile" >/dev/null 2>&1 || { > exec 9>"$lockfile" || { ``` It worked without any changes to create_lxc.sh if I only used defaults to create the proxmox backup server. This doesn't work for me since I need to add a vlan. There are some other issues when using a configuration file, but I will open another issue for that. I attached the two relevant logs. [proxmox-backup-server-success.txt](https://github.com/user-attachments/files/21216085/proxmox-backup-server-success.txt) [proxmox-backups-server-failed.txt](https://github.com/user-attachments/files/21216086/proxmox-backups-server-failed.txt) btw, debugging this is not easy. I had to download build.func, create_lxc.sh, and proxmox-backup-server.sh locally and then update the various imports of those files to use the local copy. I also had to uncomment the VERBOSE setting in create_lxc.sh. I could have at least figured out where the problem was if the VERBOSE setting was used in create_lxc.sh. I still would have had to download things locally to figure out the fix.
saavagebueno commented 2025-11-20 05:11:03 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 22, 2025):

and now?

@MickLesk commented on GitHub (Jul 22, 2025): and now?
saavagebueno commented 2025-11-20 05:11:03 -05:00
Author
Owner
Copy Link

@teohz commented on GitHub (Jul 23, 2025):

I have been getting similar errors on multiple scripts, just started to look into it myself.
In my most recent case - LinkWarden.
Verbose mode starts showing issues at later build stages - starts with timeouts:

FetchError: request to https://fonts.googleapis.com/css2?family=Bentham:wght@400&display=swap failed, reason:                            at ClientRequest.<anonymous> (/opt/linkwarden/node_modules/next/dist/compiled/node-fetch/index.js:1:65756)                           at ClientRequest.emit (node:events:518:28)                                                                                           at ClientRequest.emit (node:domain:489:12)                                                                                           at emitErrorEvent (node:_http_client:104:11)                                                                                         at TLSSocket.socketErrorListener (node:_http_client:518:5)                                                                           at TLSSocket.emit (node:events:518:28)                                                                                               at TLSSocket.emit (node:domain:489:12)                                                                                               at emitErrorNT (node:internal/streams/destroy:170:8)                                                                                 at emitErrorCloseNT (node:internal/streams/destroy:129:3)                                                                            at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {                                                   type: 'system',                                                                                                                      errno: 'ETIMEDOUT',                                                                                                                  code: 'ETIMEDOUT'                                                                                                                  }

then 'finisheh' with compile error:

Failed to compile.                                                                                                                                                                                                                                                        components/Preservation/ReadableView.tsx                                                                                             `next/font` error:                                                                                                                   Failed to fetch `Bentham` from Google Fonts.                                                                                                                                                                                                                              components/Preservation/ReadableView.tsx                                                                                             `next/font` error:                                                                                                                   Failed to fetch `Caveat` from Google Fonts.                                                                                                                                                                                                                               components/TextStyleDropdown.tsx                                                                                                     `next/font` error:                                                                                                                   Failed to fetch `Bentham` from Google Fonts.                                                                                                                                                                                                                              components/TextStyleDropdown.tsx                                                                                                     `next/font` error:                                                                                                                   Failed to fetch `Caveat` from Google Fonts.                                                                                                                                                                                                                                                                                                                                                                    > Build failed because of webpack errors                                                                                             error Command failed with exit code 1.                                                                                               info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.                                                 error Command failed.                                                                                                                Exit code: 1                                                                                                                         Command: /usr/bin/node                                                                                                               Arguments: /usr/lib/node_modules/yarn/lib/cli.js build                                                                               Directory: /opt/linkwarden/apps/web                                                                                                  Output:                                                                 

info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command.                                           error Command failed with exit code 1.                                                                                               info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.                                                                                                                                                                                      [ERROR] in line 63: exit code 0: while executing command $STD yarn web:build                                                                                                                                                                                              [ERROR] in line 1281: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/"$var_install".sh)" $?

I get all failing scripts will have different issues but all when not in verbose spit out similar error.

[ERROR] in line 1281: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/"$var_install".sh)" $?

Default installation failed the same way.
Now that I wrote all the above, I have a small suspicion (due to timeouts) that firewall may be a reason - unbound/pihole/etc with blocklists could be blocking some of the sources that are pulled from google domains like:

FetchError: request to https://fonts.googleapis.com/css2?family=Bentham:wght@400&display=swap failed, reason:

(EDIT: removing all blocklists did not help, the outcome is exactly the same)

Ascii-cast from the last failed attempt (with 'timestamps'/'markers') if anyone can't reproduce the issue themselves:

asciicast

@teohz commented on GitHub (Jul 23, 2025): I have been getting similar errors on multiple scripts, just started to look into it myself. In my most recent case - LinkWarden. Verbose mode starts showing issues at later build stages - starts with timeouts: ```bash FetchError: request to https://fonts.googleapis.com/css2?family=Bentham:wght@400&display=swap failed, reason: at ClientRequest.<anonymous> (/opt/linkwarden/node_modules/next/dist/compiled/node-fetch/index.js:1:65756) at ClientRequest.emit (node:events:518:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:104:11) at TLSSocket.socketErrorListener (node:_http_client:518:5) at TLSSocket.emit (node:events:518:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { type: 'system', errno: 'ETIMEDOUT', code: 'ETIMEDOUT' } ``` then 'finisheh' with compile error: ```bash Failed to compile. components/Preservation/ReadableView.tsx `next/font` error: Failed to fetch `Bentham` from Google Fonts. components/Preservation/ReadableView.tsx `next/font` error: Failed to fetch `Caveat` from Google Fonts. components/TextStyleDropdown.tsx `next/font` error: Failed to fetch `Bentham` from Google Fonts. components/TextStyleDropdown.tsx `next/font` error: Failed to fetch `Caveat` from Google Fonts. > Build failed because of webpack errors error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed. Exit code: 1 Command: /usr/bin/node Arguments: /usr/lib/node_modules/yarn/lib/cli.js build Directory: /opt/linkwarden/apps/web Output: info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. [ERROR] in line 63: exit code 0: while executing command $STD yarn web:build [ERROR] in line 1281: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/"$var_install".sh)" $? ``` I get all failing scripts will have different issues but all when not in verbose spit out similar error. ```bash [ERROR] in line 1281: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVE/raw/branch/main/install/"$var_install".sh)" $? ``` Default installation failed the same way. Now that I wrote all the above, I have a small suspicion (due to timeouts) that firewall may be a reason - unbound/pihole/etc with blocklists could be blocking some of the sources that are pulled from google domains like: ```bash FetchError: request to https://fonts.googleapis.com/css2?family=Bentham:wght@400&display=swap failed, reason: ``` (EDIT: removing all blocklists did not help, the outcome is exactly the same) Ascii-cast from the last failed attempt (with 'timestamps'/'markers') if anyone can't reproduce the issue themselves: [![asciicast](https://asciinema.org/a/cLngbB3FFZ1F0wmEo9D6HKThC.svg)](https://asciinema.org/a/cLngbB3FFZ1F0wmEo9D6HKThC?t=1270)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1474
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?