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 13 Packages Projects Releases 10 Wiki Activity

Zitadel - Installs but only shows {"code":5, "message":"Not Found"} when going to console #1463

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

Originally created by @tradiuz on GitHub (Aug 14, 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 12

📝 Provide a clear and concise description of the issue.

The Zitadel installer script does not appear to be functional at this time.

🔄 Steps to reproduce the issue.

Run the script.

It states ✖️ Failed to install postgresql-17-common

❌ Paste the full error output (if available).

Going to the console URL, just returns: {"code":5, "message":"Not Found"}

🖼️ Additional context (optional).

When logging into the LXC and connecting to psql, there are no tables inthe zitadel db, either, so it seems like something in the initial setup is failing somewhat silently (potentially the postgresql-17-common pkg, which should be ) and not stopping the install process.

root@zitadel:~# psql zitadel
psql (17.6 (Debian 17.6-1.pgdg12+1))
Type "help" for help.

zitadel=# \l
                                                     List of databases
   Name    |  Owner   | Encoding | Locale Provider |   Collate   |    Ctype    | Locale | ICU Rules |   Access privileges
-----------+----------+----------+-----------------+-------------+-------------+--------+-----------+-----------------------
 postgres  | postgres | UTF8     | libc            | en_US.UTF-8 | en_US.UTF-8 |        |           |
 template0 | postgres | UTF8     | libc            | en_US.UTF-8 | en_US.UTF-8 |        |           | =c/postgres          +
           |          |          |                 |             |             |        |           | postgres=CTc/postgres
 template1 | postgres | UTF8     | libc            | en_US.UTF-8 | en_US.UTF-8 |        |           | =c/postgres          +
           |          |          |                 |             |             |        |           | postgres=CTc/postgres
 zitadel   | root     | UTF8     | libc            | en_US.UTF-8 | en_US.UTF-8 |        |           | =Tc/root             +
           |          |          |                 |             |             |        |           | root=CTc/root        +
           |          |          |                 |             |             |        |           | zitadel=CTc/root
(4 rows)

zitadel=# \dt
Did not find any relations.
zitadel=#

Edited to remove red herring of Postgres tools not installing, the issue appears to be Zitadel itself and something not initializing the app properly.

Originally created by @tradiuz on GitHub (Aug 14, 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 - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. The Zitadel installer script does not appear to be functional at this time. ### 🔄 Steps to reproduce the issue. Run the script. It states ` ✖️ Failed to install postgresql-17-common` ### ❌ Paste the full error output (if available). Going to the console URL, just returns: `{"code":5, "message":"Not Found"}` ### 🖼️ Additional context (optional). When logging into the LXC and connecting to psql, there are no tables inthe zitadel db, either, so it seems like something in the initial setup is failing somewhat silently (potentially the `postgresql-17-common` pkg, which should be ) and not stopping the install process. ``` root@zitadel:~# psql zitadel psql (17.6 (Debian 17.6-1.pgdg12+1)) Type "help" for help. zitadel=# \l List of databases Name | Owner | Encoding | Locale Provider | Collate | Ctype | Locale | ICU Rules | Access privileges -----------+----------+----------+-----------------+-------------+-------------+--------+-----------+----------------------- postgres | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | template0 | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =c/postgres + | | | | | | | | postgres=CTc/postgres template1 | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =c/postgres + | | | | | | | | postgres=CTc/postgres zitadel | root | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =Tc/root + | | | | | | | | root=CTc/root + | | | | | | | | zitadel=CTc/root (4 rows) zitadel=# \dt Did not find any relations. zitadel=# ``` **Edited to remove red herring of Postgres tools not installing, the issue appears to be Zitadel itself and something not initializing the app properly.**
OVERLORD added the bugexternal labels 2026-02-05 00:56:03 +03:00
OVERLORD commented 2026-02-05 00:56:10 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 14, 2025):

Ignore it, some scripts with older system fallback to psql 16 where common needed. Its Just an hint. Psql17 include this

@MickLesk commented on GitHub (Aug 14, 2025): Ignore it, some scripts with older system fallback to psql 16 where common needed. Its Just an hint. Psql17 include this
OVERLORD commented 2026-02-05 00:56:15 +03:00
Author
Owner
Copy Link

@tradiuz commented on GitHub (Aug 14, 2025):

@MickLesk - That doesn't solve the issue that it still showing {"code":5, "message":"Not Found"} and no tables in psql. (See additional comments, above)

@tradiuz commented on GitHub (Aug 14, 2025): @MickLesk - That doesn't solve the issue that it still showing `{"code":5, "message":"Not Found"}` and no tables in psql. (See additional comments, above)
OVERLORD commented 2026-02-05 00:56:18 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 14, 2025):

Then its another issue

@dave-yap can you take a Look? Maybe in 4.0 Changed something

@MickLesk commented on GitHub (Aug 14, 2025): Then its another issue @dave-yap can you take a Look? Maybe in 4.0 Changed something
OVERLORD commented 2026-02-05 00:56:25 +03:00
Author
Owner
Copy Link

@tradiuz commented on GitHub (Aug 14, 2025):

I'll edit the initial post if you'll re-open the issue.

@tradiuz commented on GitHub (Aug 14, 2025): I'll edit the initial post if you'll re-open the issue.
OVERLORD commented 2026-02-05 00:56:30 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 14, 2025):

Should be fixed after #6826 merges

@tremor021 commented on GitHub (Aug 14, 2025): Should be fixed after #6826 merges
OVERLORD commented 2026-02-05 00:56:33 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 14, 2025):

Its not only the Common issue

@MickLesk commented on GitHub (Aug 14, 2025): Its not only the Common issue
OVERLORD commented 2026-02-05 00:56:37 +03:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Aug 14, 2025):

I'll have a look when I'm back and have the time.

@dave-yap commented on GitHub (Aug 14, 2025): I'll have a look when I'm back and have the time.
OVERLORD commented 2026-02-05 00:56:40 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 15, 2025):

https://zitadel.com/docs/self-hosting/deploy/linux

Last updated on Aug 13, 2025 by Elio Bischof

This needs to be checked

@tremor021 commented on GitHub (Aug 15, 2025): `https://zitadel.com/docs/self-hosting/deploy/linux` `Last updated on Aug 13, 2025 by Elio Bischof` This needs to be checked
OVERLORD commented 2026-02-05 00:56:43 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 15, 2025):

msg_info "Creating Services"
cat <<EOF >/etc/systemd/system/zitadel.service
[Unit]
Description=ZITADEL Identiy Server
After=network.target postgresql.service
Wants=postgresql.service

[Service]
Type=simple
User=zitadel
Group=zitadel
ExecStart=/usr/local/bin/zitadel start --masterkeyFile "/opt/zitadel/.masterkey" --config "/opt/zitadel/config.yaml"
Restart=always
RestartSec=5
TimeoutStartSec=0

# Security Hardening options
ProtectSystem=full
ProtectHome=true
PrivateTmp=true
NoNewPrivileges=true

[Install]
WantedBy=multi-user.target
EOF
systemctl enable -q --now zitadel
msg_ok "Created Services"

msg_info "Zitadel initial setup"
zitadel start-from-init --masterkeyFile /opt/zitadel/.masterkey --config /opt/zitadel/config.yaml &>/dev/null &
sleep 60
kill $(lsof -i | awk '/zitadel/ {print $2}' | head -n1)
useradd zitadel
msg_ok "Zitadel initialized"

Service start errors because user zitadel is added afterwards. This script definitely needs to be checked @dave-yap

@tremor021 commented on GitHub (Aug 15, 2025): ```bash msg_info "Creating Services" cat <<EOF >/etc/systemd/system/zitadel.service [Unit] Description=ZITADEL Identiy Server After=network.target postgresql.service Wants=postgresql.service [Service] Type=simple User=zitadel Group=zitadel ExecStart=/usr/local/bin/zitadel start --masterkeyFile "/opt/zitadel/.masterkey" --config "/opt/zitadel/config.yaml" Restart=always RestartSec=5 TimeoutStartSec=0 # Security Hardening options ProtectSystem=full ProtectHome=true PrivateTmp=true NoNewPrivileges=true [Install] WantedBy=multi-user.target EOF systemctl enable -q --now zitadel msg_ok "Created Services" msg_info "Zitadel initial setup" zitadel start-from-init --masterkeyFile /opt/zitadel/.masterkey --config /opt/zitadel/config.yaml &>/dev/null & sleep 60 kill $(lsof -i | awk '/zitadel/ {print $2}' | head -n1) useradd zitadel msg_ok "Zitadel initialized" ``` Service start errors because user `zitadel` is added afterwards. This script definitely needs to be checked @dave-yap
OVERLORD commented 2026-02-05 00:56:46 +03:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Aug 15, 2025):

Having a look at my script that I written initially, it was systemctl enable -q zitadel.service but not systemctl enable -q --now zitadel.service. Maybe it is indeed failing as the user is only added after the service has been started without the user...

EDIT: I do believe it is failing because of that line as Zitadel has to be initialized by the line zitadel start-from-init before the service can be started per se.

@dave-yap commented on GitHub (Aug 15, 2025): Having a look at my script that I written initially, it was `systemctl enable -q zitadel.service` but not `systemctl enable -q --now zitadel.service`. Maybe it is indeed failing as the user is only added after the service has been started without the user... EDIT: I do believe it is failing because of that line as Zitadel has to be initialized by the line `zitadel start-from-init` before the service can be started per se.
OVERLORD commented 2026-02-05 00:56:51 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 15, 2025):

Then its my bad, gonna revert a change on that line. Somehow i missed that you're initializing it later down in the script. PR is up

@tremor021 commented on GitHub (Aug 15, 2025): Then its my bad, gonna revert a change on that line. Somehow i missed that you're initializing it later down in the script. PR is up
OVERLORD commented 2026-02-05 00:56:55 +03:00
Author
Owner
Copy Link

@ruehcep commented on GitHub (Aug 16, 2025):

Hi there, I am still running into this issue. Has it been solved?

@ruehcep commented on GitHub (Aug 16, 2025): Hi there, I am still running into this issue. Has it been solved?
OVERLORD commented 2026-02-05 00:56:58 +03:00
Author
Owner
Copy Link

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

@dave-yap well, its not my change that broke it it seems. Something else is going on

@tremor021 commented on GitHub (Aug 16, 2025): @dave-yap well, its not my change that broke it it seems. Something else is going on
OVERLORD commented 2026-02-05 00:57:02 +03:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Aug 17, 2025):

Indeed... I'll take a closer look when I'm free, currently on my vacation so can't look into it properly yet.

@dave-yap commented on GitHub (Aug 17, 2025): Indeed... I'll take a closer look when I'm free, currently on my vacation so can't look into it properly yet.
OVERLORD commented 2026-02-05 00:57:07 +03:00
Author
Owner
Copy Link

@AJL1-Hub commented on GitHub (Aug 19, 2025):

Indeed... I'll take a closer look when I'm free, currently on my vacation so can't look into it properly yet.

@dave-yap I hope that you are having/had a wonderful and blessed vacation. We are looking forward to a fix when you get back and able to look into the problem. Until then stay safe and have fun!

@AJL1-Hub commented on GitHub (Aug 19, 2025): > Indeed... I'll take a closer look when I'm free, currently on my vacation so can't look into it properly yet. @dave-yap I hope that you are having/had a wonderful and blessed vacation. We are looking forward to a fix when you get back and able to look into the problem. Until then stay safe and have fun!
OVERLORD commented 2026-02-05 00:57:13 +03:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Aug 19, 2025):

@tremor021 Looking back at my own repo, the initial script uses apt install postgresql postgresql-common, but the current refactored script uses PG_VERSION="17" setup_postgresql. It installs postgresql-17, without postgresql-common.

Maybe that's causing the error?

@dave-yap commented on GitHub (Aug 19, 2025): @tremor021 Looking back at my own repo, the initial script uses `apt install postgresql postgresql-common`, but the current refactored script uses `PG_VERSION="17" setup_postgresql`. It installs postgresql-17, without postgresql-common. Maybe that's causing the error?
OVERLORD commented 2026-02-05 00:57:16 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 19, 2025):

common is part of psql17

Image
@MickLesk commented on GitHub (Aug 19, 2025): common is part of psql17 <img width="710" height="254" alt="Image" src="https://github.com/user-attachments/assets/50f0401f-54e2-4025-97b1-01dd76ea7b2e" />
OVERLORD commented 2026-02-05 00:57:18 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 19, 2025):

Isn't common included in pg17? Its not a separate package?

@tremor021 commented on GitHub (Aug 19, 2025): Isn't common included in pg17? Its not a separate package?
OVERLORD commented 2026-02-05 00:57:21 +03:00
Author
Owner
Copy Link

@dave-yap commented on GitHub (Aug 20, 2025):

@MickLesk Did you manage to get the Zitadel LXC to install?

Looking at the initial issue post, I see the error when installing postgresql-17-common, was there an issue with the install function for postgresql? Sorry but will have to delay the actual troubleshooting...

@dave-yap commented on GitHub (Aug 20, 2025): @MickLesk Did you manage to get the Zitadel LXC to install? Looking at the initial issue post, I see the error when installing `postgresql-17-common`, was there an issue with the install function for postgresql? Sorry but will have to delay the actual troubleshooting...
OVERLORD commented 2026-02-05 00:57:24 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 20, 2025):

Yeah its installing, but the Frontend doesnt load. Error Message 5. No Logs, no Issues in Journalctl

@MickLesk commented on GitHub (Aug 20, 2025): Yeah its installing, but the Frontend doesnt load. Error Message 5. No Logs, no Issues in Journalctl
OVERLORD commented 2026-02-05 00:57:28 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 20, 2025):

its a migration issue

Image v3.3.6 (latest v3.x.x stable) installs fine.

v4.x.x breaks with current install method. Selfhosting docs are updated on Aug. 15. The script needs to be checked again.

@MickLesk want me to pin the version until we refactor this?

@tremor021 commented on GitHub (Aug 20, 2025): its a migration issue <img width="950" height="599" alt="Image" src="https://github.com/user-attachments/assets/77fc4390-71d9-4aae-9190-e129c359e4f8" /> v3.3.6 (latest v3.x.x stable) installs fine. v4.x.x breaks with current install method. Selfhosting docs are updated on Aug. 15. The script needs to be checked again. @MickLesk want me to pin the version until we refactor this?
OVERLORD commented 2026-02-05 00:57:31 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 20, 2025):

I just completely reinstalled it on a fresh Debian 12 LXC using their official instructions. It causes the same problem. template uses psql16

i think, i create an issue at there repo.

Image Image

Issue created here: https://github.com/zitadel/zitadel/issues/10526

@MickLesk commented on GitHub (Aug 20, 2025): I just completely reinstalled it on a fresh Debian 12 LXC using their official instructions. It causes the same problem. template uses psql16 i think, i create an issue at there repo. <img width="670" height="241" alt="Image" src="https://github.com/user-attachments/assets/7b34e45a-9801-4368-a2b4-cceecf3ed34e" /> <img width="328" height="91" alt="Image" src="https://github.com/user-attachments/assets/4295d01c-fccb-4257-b173-851ba949ef6b" /> Issue created here: https://github.com/zitadel/zitadel/issues/10526
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 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#1463
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?