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

Zitadel - Fails at "initial setup" #645

New Issue
Closed
opened 2025-11-20 04:51:35 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 04:51:35 -05:00
Owner
Copy Link

Originally created by @PouletteMC on GitHub (Mar 4, 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 "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/zitadel.sh)"

📝 Provide a clear and concise description of the issue.

Running the install script fails when initializing Zitadel itself.

Verbose logs don't add any meaningful intel

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. Start the script
  2. Select default settings
  3. Wait for the Zitadel initialisation step
  4. After a while it fails

❌ Paste the full error output (if available).

✔️ Updated Container OS
✔️ Installed Dependecies
✔️ Installed PostgreSQL
✔️ Installed Zitadel
✔️ Installed Zitadel Enviroments
✔️ Created Services
⠸kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
⠴
[ERROR] in line 126: exit code 0: while executing command kill $(lsof -i | awk '/zitadel/ {print $2}' | head -n1)

🖼️ Additional context (optional).

Tried running on three different nodes with wildly different specs, no luck. The container is created and running but the app itself fails to install

Originally created by @PouletteMC on GitHub (Mar 4, 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 "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/zitadel.sh)" ### 📝 Provide a clear and concise description of the issue. Running the install script fails when initializing Zitadel itself. Verbose logs don't add any meaningful intel ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. 1. Start the script 2. Select default settings 3. Wait for the Zitadel initialisation step 4. After a while it fails ### ❌ Paste the full error output (if available). ✔️ Updated Container OS ✔️ Installed Dependecies ✔️ Installed PostgreSQL ✔️ Installed Zitadel ✔️ Installed Zitadel Enviroments ✔️ Created Services ⠸kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] ⠴ [ERROR] in line 126: exit code 0: while executing command kill $(lsof -i | awk '/zitadel/ {print $2}' | head -n1) ### 🖼️ Additional context (optional). Tried running on three different nodes with wildly different specs, no luck. The container is created and running but the app itself fails to install
saavagebueno added the external label 2025-11-20 04:51:35 -05:00
saavagebueno commented 2025-11-20 04:51:36 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 4, 2025):

@dave-yap

@MickLesk commented on GitHub (Mar 4, 2025): @dave-yap
saavagebueno commented 2025-11-20 04:51:36 -05:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Mar 4, 2025):

Running the script gives me the same error too. When troubleshooting and running the step that precedes the kill process line, it seems that there is an issue setting it up. It might be a Zitadel issue as it had happened in the past: Zitadel Issue #9300. I believe it has to be fixed on Zitadel's end, but for now since the script has been modified to always pull the latest and not pinned to any version, it will continue to fail sadly.

For now, if you'd like to use Zitadel, you can use my repo's script which is currently pinned to v2.68.0. As always, exercise caution and read through the source code before using it.

It can be ran using the following command:

bash -c "$(wget -qLO - https://raw.githubusercontent.com/dave-yap/ProxmoxVE/refs/heads/test/ct/test.sh)"

EDIT: I have since opened an issue on Zitadel's repo and hopefully they'll fix the issue soon.

@dave-yap commented on GitHub (Mar 4, 2025): Running the script gives me the same error too. When troubleshooting and running the step that precedes the kill process line, it seems that there is an issue setting it up. It might be a Zitadel issue as it had happened in the past: [Zitadel Issue #9300](https://github.com/zitadel/zitadel/issues/9300#issue-2828566793). I believe it has to be fixed on Zitadel's end, but for now since the script has been modified to always pull the latest and not pinned to any version, it will continue to fail sadly. For now, if you'd like to use Zitadel, you can use my repo's script which is currently pinned to v2.68.0. As always, exercise caution and read through the source code before using it. It can be ran using the following command: ```bash -c "$(wget -qLO - https://raw.githubusercontent.com/dave-yap/ProxmoxVE/refs/heads/test/ct/test.sh)"``` EDIT: I have since opened an issue on Zitadel's repo and hopefully they'll fix the issue soon.
saavagebueno commented 2025-11-20 04:51:36 -05:00
Author
Owner
Copy Link

@PouletteMC commented on GitHub (Mar 5, 2025):

Thank you for that info and script, I ended up using PocketID instead. I might try Zitadel again if (when) they fix the issue

@PouletteMC commented on GitHub (Mar 5, 2025): Thank you for that info and script, I ended up using PocketID instead. I might try Zitadel again if (when) they fix the issue
saavagebueno commented 2025-11-20 04:51:36 -05:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Mar 6, 2025):

It should be fixed now with the new release.

@dave-yap commented on GitHub (Mar 6, 2025): It should be fixed now with the new release.
saavagebueno commented 2025-11-20 04:51:37 -05:00
Author
Owner
Copy Link

@PouletteMC commented on GitHub (Mar 6, 2025):

Thanks for the update, I'll try again ! Wasn't expecting such a quick fix

@PouletteMC commented on GitHub (Mar 6, 2025): Thanks for the update, I'll try again ! Wasn't expecting such a quick fix
saavagebueno commented 2025-11-20 04:51:37 -05:00
Author
Owner
Copy Link

@PouletteMC commented on GitHub (Mar 6, 2025):

The install completed successfully, thanks for the help @dave-yap !

@PouletteMC commented on GitHub (Mar 6, 2025): The install completed successfully, thanks for the help @dave-yap !
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 external
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#645
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?