FHi there
This is an odd error, I have not yet seen this one
The first thing that pops to my mind is a resource starvation (even though zitadel works just fine with 1 cpu)
Can you share your configs and/or more details about your setup?
This is an odd error, I have not yet seen this one
The first thing that pops to my mind is a resource starvation (even though zitadel works just fine with 1 cpu)
Can you share your configs and/or more details about your setup?
FHm, an initial glance did not trigger anything that i could tell broken
Resource wise you defenitly should be fine.
What happens if you use the latest version v2.14.2?
Resource wise you defenitly should be fine.
What happens if you use the latest version v2.14.2?
FIt looks to me you use stable
Fthat is a few versions behind.
FYeah the log is still little noisy
FWhat happens on the GUI side?
FHm need to check those errors with a colleague.
Is it now always a gateway timeout or still the same behaviour?
Is it now always a gateway timeout or still the same behaviour?
FI think currently not. What happens if you start over with a empty database?
FOur postgres support is still relatively fresh and maybe we hit a bug
and maybe we hit a bugFA new db should be totally sufficient. What Postgres version are you running?
FReally strange the assets warning should not block things.
Let me check with @livio and @adlerhurst tomorrow
Let me check with @livio and @adlerhurst tomorrow