FEach ZITADEL will need to have a ZITADEL project in an organization.
Moving is currently no possible, so we recommend that you start with an organization that only contains the ZITADEL project and create as many new orgs as you need for your needs.
Btw. Org deletion just landed in our API and should be available in our GUI soon as well (so you cannot yet delete orgs anyway)
Moving is currently no possible, so we recommend that you start with an organization that only contains the ZITADEL project and create as many new orgs as you need for your needs.
Btw. Org deletion just landed in our API and should be available in our GUI soon as well (so you cannot yet delete orgs anyway)
FThe domains you should be able to delete. Do you experience a problem while deleting?
Fi see, are you self-hosting zitadel?
FOk, great
in that case it is important that you setup two things:
1) The name the whole system is using also called External
2) How the name of the org should be for the default org
This should give you zitadel.my.domain as the name.
in that case it is important that you setup two things:
1) The name the whole system is using also called External
2) How the name of the org should be for the default org
This should give you zitadel.my.domain as the name.
F
FHappy to assist
Fhm, did create a new zitadel or changed it on a running system?
FOk can you try with a new database.
Of the top of my head i think only that works correctly
Of the top of my head i think only that works correctly
FAh yes i meant like a "fresh" setup.
you can either create a new DB in Cockroach or recreate the CockroachDB
Kind of depending on your setup
you can either create a new DB in Cockroach or recreate the CockroachDB
Kind of depending on your setup
FHm what version are you running ?
FCan you tear it down an try the newest version. We fixed many bug since the version 2
FMhm the time Problem is a storage side issue. This sounds like something is off with the cockroachdb
FSound like a ntp issue to me
FCan you check the ntp settings on that machine
FIt really looks like there is a problem in that space since this error is being raised from the database
FHow are you running the db? As container?
FHm is the time of the machine correct ?
FStrange, honestly the only thing I can point to is a time issue with the db.
What happens if you tear it down once again
What happens if you tear it down once again
Fsorry for my late reply, but let me check with the team why this happend
FSo far I understood you backuped and restored the database right?
Can you provide me the commands you used for our debugging?
Can you provide me the commands you used for our debugging?