ZITADEL

Z

ZITADEL

ZITADEL - Identity infrastructure, simplified for you.

Join

questions-help-bugs

product-feedback-requests

Very slow migration (2.61.0 --> 3.3.0)

Hi team! First of all, thank you for this amazing piece of software! Really great dev experience so far. We are self-hosting Zitadel on Kubernetes. As we continue developing our application that will eventually integrate with Zitadel, we decide to update our dependencies, including Zitadel itself. We upgraded from 2.61.0 to 3.3.0. The database contains ~84,000 users....

Zitadel Database disk usage

Hello the DB (PG) used by our Zitadel instance is consuming a lot of disk space and growning - is there any resource that give specific pointers on optimizations? e.g.: clean up routines, delete old data, etc. asking only for Zitadel specific stuff, PG generic stuff we can handle on our own, not to wast anyone's time 😂 Thanks!...

Each organisation with its own custom domain

I wanted to know if with Zitadel self-hosted, it was possible to have org1.mydomain.ch and org2.mydomain.ch with their associated branding (with zitadel.mydomain.ch as EXTERNALDOMAIN)? I've tested different configurations according to the documentation but adding a domain to a self-hosted instance doesn't work at all whether it's the v1 or v2 API. ...

Postgres 16 --> 17 Documentation

Hi folks. Home user here who's slowly learning how to self-host things over the past couple of months. I went to update my Zitadel docker container today, and noticed that on the lastest compose.yaml deployment example, we now use postgres 17. My existing setup uses postgres 16 from when I first created the container back in March of this year. Is there any documentation on how to migrate from v16 to v17? I've looked through release notes, this server, github issues etc - but can only find issues relating to the old cockroach migration....

V2 api self organization create flow is not working correctly

Hi Team, We are currently migrating to the V2 API. We are experiencing some strange behaviour when a customer wants to signup for our system. When a new customer want to singup we redirect them to: /ui/login/register/org. The customer fills in all information and can then sign in. ...
No description

Deleting Bulk Users

Hey @Rajat , I am in need to clean up unwanted/unused users created in zitadel. It is actually 3 digit count, which means manually deleting each user will be difficult and time taking process. I directly accessed db and deleted the users with certain key using dbquery, but yet I can see those users listed in the console. By search I got to know like as zitadel is event based so it will be displayed based on the event. This db query check I have done in another instance not in the actual instance. Is there any ways to handle this?...

Not able to use terraform 3.3.0

Described my issue in detail here: https://github.com/zitadel/zitadel/discussions/9290#discussioncomment-13514639 basically even after having permissions at all levels, not able to create resources with terraform(provider 2.2.0)...

Connection reset by peer

Ever since upgrading to v2.71.9 and henceforth, I am seeing many connection reset errors like the following. Is there some configuration that I can tweak to mitigate this?
get user from zitadel, error: rpc error: code = Unavailable desc = error reading from server: read tcp 10.230.54.27:55668->34.233.181.143:443: read: connection reset by peer "}
get user from zitadel, error: rpc error: code = Unavailable desc = error reading from server: read tcp 10.230.54.27:55668->34.233.181.143:443: read: connection reset by peer "}
...

when using zitadel api with protobuf .

export async function systemAPIToken() { const token = { audience: process.env.AUDIENCE, userID: process.env.SYSTEM_USER_ID, token: Buffer.from(process.env.SYSTEM_USER_PRIVATE_KEY, "base64").toString(...
No description

Permanently periodically unable to update "projections.notifications" state error in zitadel logs

Zitadel Helm chart: 8.11.2 Zitadel app version: v2.67.2 Self hosted Kubernetes with Postgresql 15. We are getting permanent periodic errors on the notifications projections:...

First Instance Policy not getting applied

``` LoginPolicy: AllowUsernamePassword: true # ZITADEL_DEFAULTINSTANCE_LOGINPOLICY_ALLOWUSERNAMEPASSWORD AllowRegister: true # ZITADEL_DEFAULTINSTANCE_LOGINPOLICY_ALLOWREGISTER AllowExternalIDP: true # ZITADEL_DEFAULTINSTANCE_LOGINPOLICY_ALLOWEXTERNALIDP (social login)...

Custom SMTP Didn't Send any Email

I have config my custom SMTP to send email first it work last email that was send is last week ago than it didn't send any email from that on I have check - Is my email SMTP provider still work? - Yes It still work I can still manually sent with NOVU but it not work on my zitadel some how...
No description

Can i create virtual instances in zitadel selfhosted?

This comes from the confusion that what should even be the CUSTOM DOMAIN here, and what would be the token be? (from an existing instance?) https://zitadel.com/docs/apis/resources/system/system-service-create-instance ...

How stable is the V2 API

Is the V1 API deprecated? I am just getting started w zitadel and I see some posts about the v1 and v2, also features flags related to that. Since I am just starting out I rather not deal with any unstable behaviour, is it fine to go along with the v1 for now as it's probably more mature? (I see a lot of v2 issues in this discord thread, so somewhat confused)

You can remove yourself(the only manager) from an org

I am not sure if this is a bug or a feature but after doing this I am locked out of my org?

Does --init-projection not work w Docker?

I updated my externalDomain, which workerd but my primary domain of the org is still stuck in the old version. I've ran zitadel setup and restarted zitadel aswell with no luck. found this issue: https://github.com/zitadel/zitadel/discussions/8351#discussioncomment-10137078 ...

Add a custom domain using v2 api

Hello, is the documentation https://zitadel.com/docs/apis/resources/instance_service_v2/instance-service-add-custom-domain up to date ? I'm not able to add a custom domain to my self-hosted environment ...

Organization API v2

Hi, I am using the organization calls from v1 especially for metadata stuff. The docs now mark nearly all methods from v1 as deprecated, but I did not found the new v2 organization calls in the docs to set or get org metadata. I've seen that the task in GitHub to add the v2 API methods for organizations is already finished. Can I already implement these calls or are they not out yet? Since they are missing in the docs....

V2 email for password setup

Hi Team, I have migrated to zitadel v2 API from v1 to avoid storing password. In v2 we can control sending email to set password, but in the verification mail it is asking for password to be set. How to avoid this? I don't want the user initialization or password set to be automated during user creation. I want it to be separately done by triggering API....

Error on authorization after creation passkey via API

Environment: self hosting I am doing the flow described here https://zitadel.com/docs/guides/integrate/login-ui/passkey#login-with-passkey to test passkey flow before development. I am sending requests to Zitadel using Postman....
No description