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

Zitadel install script is broken because latest ZITADEL release does not include a zitadel-linux-amd64.tar.gz file. #1804

New Issue
Closed
opened 2026-02-05 02:18:04 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-05 02:18:04 +03:00
Owner
Copy Link

Originally created by @grous0 on GitHub (Oct 16, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Zitadel

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.0.10

📝 Provide a clear and concise description of the issue.

Latest release of Zitadel GitHub repo does not include a zitadel-linux-amd64.tar.gz file. So the script fails with something like "zitadel-linux-amd64.tar.gz file doesn't exist."

🔄 Steps to reproduce the issue.

  1. Run the script in PVE Node with default settings
  2. Container gets created
  3. Script fails because of fetch_and_deploy_gh_release function can't find the release file thats mentioned in the script.

❌ Paste the full error output (if available).

  ✔️   Installed PostgreSQL
   ✖️   No asset matching 'zitadel-linux-amd64.tar.gz' found

[ERROR] in line 42: 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).

The releases are generated with GitHub Actions CI/CD.

Originally created by @grous0 on GitHub (Oct 16, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Zitadel ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zitadel.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.0.10 ### 📝 Provide a clear and concise description of the issue. Latest release of Zitadel GitHub repo does not include a `zitadel-linux-amd64.tar.gz` file. So the script fails with something like "zitadel-linux-amd64.tar.gz file doesn't exist." ### 🔄 Steps to reproduce the issue. 1. Run the script in PVE Node with default settings 2. Container gets created 3. Script fails because of fetch_and_deploy_gh_release function can't find the release file thats mentioned in the script. ### ❌ Paste the full error output (if available). ``` ✔️ Installed PostgreSQL ✖️ No asset matching 'zitadel-linux-amd64.tar.gz' found [ERROR] in line 42: 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). The releases are generated with GitHub Actions CI/CD.
OVERLORD added the external label 2026-02-05 02:18:04 +03:00
OVERLORD commented 2026-02-05 02:18:08 +03:00
Author
Owner
Copy Link

@grous0 commented on GitHub (Oct 16, 2025):

It looks like Zitadel trying to fix this issue. https://github.com/zitadel/zitadel/issues/10896#issue-3508899567

But its been 3 damn days...

@grous0 commented on GitHub (Oct 16, 2025): It looks like Zitadel trying to fix this issue. https://github.com/zitadel/zitadel/issues/10896#issue-3508899567 But its been 3 damn days...
OVERLORD commented 2026-02-05 02:18:13 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 16, 2025):

Nothing we can really do until they fix there stuff sadly.

@michelroegl-brunner commented on GitHub (Oct 16, 2025): Nothing we can really do until they fix there stuff sadly.
OVERLORD commented 2026-02-05 02:18:15 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 16, 2025):

Duplicate of other issues

@MickLesk commented on GitHub (Oct 16, 2025): Duplicate of other issues
OVERLORD commented 2026-02-05 02:18:16 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Oct 16, 2025):

#8308

@tremor021 commented on GitHub (Oct 16, 2025): #8308
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 external
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#1804
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?