starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Blocky installation fails - No asset found #1655

New Issue
Closed
opened 2026-02-05 01:52:40 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 01:52:40 +03:00
Owner
Copy Link

Originally created by @ollide on GitHub (Sep 23, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Blocky

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

8.4.5

📝 Provide a clear and concise description of the issue.

When I try to install Blocky with the Proxmox Helper Script, the installation fails with the message No asset matching 'blocky_*_linux_x86_64.tar.gz' found.

I checked the Blocky repository and noticed that the release artifacts use a capital L in Linux (e.g. https://github.com/0xERR0R/blocky/releases/download/v0.26.2/blocky_v0.26.2_Linux_x86_64.tar.gz ).

I assume that this issue was introduced in the refactoring 2 weeks ago: 95e15699fb (diff-91a17c043a7a3184f7f27062f9b4ec330e4e12dc0455d0db9683ae5eb5081e9fL22)

🔄 Steps to reproduce the issue.

  1. Run the command below in the Proxmox VE Shell:
    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/blocky.sh)"
  2. Use Default Settings

❌ Paste the full error output (if available).

✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
✔️ Updated Container OS
✖️ No asset matching 'blocky_*_linux_x86_64.tar.gz' found

[ERROR] in line 16: exit code 0: while executing command return 1

[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

🖼️ Additional context (optional).

No response

Originally created by @ollide on GitHub (Sep 23, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Blocky ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/blocky.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4.5 ### 📝 Provide a clear and concise description of the issue. When I try to install Blocky with the Proxmox Helper Script, the installation fails with the message `No asset matching 'blocky_*_linux_x86_64.tar.gz' found`. I checked the Blocky repository and noticed that the release artifacts use a capital **L** in Linux (e.g. https://github.com/0xERR0R/blocky/releases/download/v0.26.2/blocky_v0.26.2_Linux_x86_64.tar.gz ). I assume that this issue was introduced in the refactoring 2 weeks ago: https://github.com/community-scripts/ProxmoxVE/commit/95e15699fba2f01f2778cf775b91f46eb429c0cc#diff-91a17c043a7a3184f7f27062f9b4ec330e4e12dc0455d0db9683ae5eb5081e9fL22 ### 🔄 Steps to reproduce the issue. 1. Run the command below in the Proxmox VE Shell: `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/blocky.sh)"` 2. Use Default Settings ### ❌ Paste the full error output (if available). ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✖️ No asset matching 'blocky_*_linux_x86_64.tar.gz' found [ERROR] in line 16: exit code 0: while executing command return 1 [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" ### 🖼️ Additional context (optional). _No response_
OVERLORD added the buginvestigation labels 2026-02-05 01:52:40 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label bug investigation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1655
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?