starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 01:06:06 +03:00

[GH-ISSUE #9868] Error in PVE 9.1.2 when running any helper script with advanced install #2149

New issue

Closed

opened 2026-02-26 12:51:29 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 12:51:29 +03:00

Owner

Originally created by @apexmbv on GitHub (Dec 11, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9868

✅ 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?

Audiobookshelf (but I get the error with any install now)

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

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

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/9.1.2/9d436f37a0ac4172 (running kernel: 6.17.2-2-pve)

📝 Provide a clear and concise description of the issue.

FYI: I cannot run a default install because I must define a VLAN for the network interface. I also do not want to enable nested containers or hardware passthrough which is what the latest helper scripts are doing by default for some reason.

Any time I try to install any LXC through the helper script, I'm getting an error on container creation

400 too many arguments

I try to pick as many defaults in the advanced install as possible but nothing seems to work

🔄 Steps to reproduce the issue.

Step 1: Run the bash script
Step 2: Fill out information pertaining to container creation
Step 3: Watch the script fail to create the container with error 400 - too many arguments

❌ Paste the full error output (if available).

pct create 112 local:vztmpl/debian-12-standard_12.12-1_amd64.tar.zst -features -hostname audiobookshelf -tags 'community-script;podcast;audiobook' -net0 name=eth0,bridge=vmbr0,ip=XXX.XXX.XXX.XXX/24,gw=XXX.XXX.XXX.XXX,tag=12 -onboot 1 -cores 2 -memory 2048 -unprivileged 0 -timezone America/New_York -rootfs local-zfs:5
tee -a /tmp/pct_create_112_20251210_221326_dbcdeef2.log
400 too many arguments
pct create [OPTIONS]
set +x

🖼️ Additional context (optional).

Originally created by @apexmbv on GitHub (Dec 11, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9868 ### ✅ 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? Audiobookshelf (but I get the error with any install now) ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/audiobookshelf.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.1.2/9d436f37a0ac4172 (running kernel: 6.17.2-2-pve) ### 📝 Provide a clear and concise description of the issue. FYI: I cannot run a default install because I must define a VLAN for the network interface. I also do not want to enable nested containers or hardware passthrough which is what the latest helper scripts are doing by default for some reason. Any time I try to install any LXC through the helper script, I'm getting an error on container creation 400 too many arguments I try to pick as many defaults in the advanced install as possible but nothing seems to work ### 🔄 Steps to reproduce the issue. Step 1: Run the bash script Step 2: Fill out information pertaining to container creation Step 3: Watch the script fail to create the container with error 400 - too many arguments ### ❌ Paste the full error output (if available). + pct create 112 local:vztmpl/debian-12-standard_12.12-1_amd64.tar.zst -features -hostname audiobookshelf -tags 'community-script;podcast;audiobook' -net0 name=eth0,bridge=vmbr0,ip=XXX.XXX.XXX.XXX/24,gw=XXX.XXX.XXX.XXX,tag=12 -onboot 1 -cores 2 -memory 2048 -unprivileged 0 -timezone America/New_York -rootfs local-zfs:5 + tee -a /tmp/pct_create_112_20251210_221326_dbcdeef2.log 400 too many arguments pct create <vmid> <ostemplate> [OPTIONS] + set +x ### 🖼️ Additional context (optional). <img width="2212" height="969" alt="Image" src="https://github.com/user-attachments/assets/8db8f970-3a03-40ba-b34d-94c0d8ff5348" />

kerem

2026-02-26 12:51:29 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:51:29 +03:00

Author

Owner

@apexmbv commented on GitHub (Dec 11, 2025):

Also, this just started happening in the past couple days. I've built 10+ last week without any issue using the advanced settings method, but this was before the helper script started asking me about GPU pass through, shares, protection, etc.

@apexmbv commented on GitHub (Dec 11, 2025): Also, this just started happening in the past couple days. I've built 10+ last week without any issue using the advanced settings method, but this was before the helper script started asking me about GPU pass through, shares, protection, etc.

kerem commented

2026-02-26 12:51:29 +03:00

Author

Owner

@apexmbv commented on GitHub (Dec 11, 2025):

After some investigation, it appears when you don't select any of the options for the "-features" parameter during the advanced install, that's what's causing the issue. The pct command is still putting the "-features" parameter in the command with no arguments and it's causing pct to freak out. I just tried with a single "feature" and the script finished without an issue (but now I have to edited the container and remove that "feature").

Would it be possible to have a conditional added to the script that says if the user doesn't select any features, to run the command without that parameter?

@apexmbv commented on GitHub (Dec 11, 2025): After some investigation, it appears when you don't select any of the options for the "-features" parameter during the advanced install, that's what's causing the issue. The pct command is still putting the "-features" parameter in the command with no arguments and it's causing pct to freak out. I just tried with a single "feature" and the script finished without an issue (but now I have to edited the container and remove that "feature"). Would it be possible to have a conditional added to the script that says if the user doesn't select any features, to run the command without that parameter?

kerem commented

2026-02-26 12:51:29 +03:00

Author

Owner

@tremor021 commented on GitHub (Dec 11, 2025):

Should be fixed when #9871 merges. Try again then

@tremor021 commented on GitHub (Dec 11, 2025): Should be fixed when #9871 merges. Try again then

kerem commented

2026-02-26 12:51:29 +03:00

Author

Owner

@apexmbv commented on GitHub (Dec 11, 2025):

Thank you for the quick response and resolution!

@apexmbv commented on GitHub (Dec 11, 2025): Thank you for the quick response and resolution!

kerem referenced this issue

2026-02-26 13:33:57 +03:00

[PR #2149] [MERGED] [Github Action] Update CHANGELOG.md #3571

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2149

No description provided.

Rows
Columns