FWith a 504 is there an error from your nginx?
Like upstream error?
Like upstream error?
FCan you share me some more info how you setup zitadel. Like deplyoment, db, cpu, memory...
FOK did you configure something in the DB settings on the zitadel config?
FWhat are your nginx Settings?
The error to me looks like nginx closes the connection to Zitadel
The error to me looks like nginx closes the connection to Zitadel
Fyou could experiment with
grpc_set_header Host $host:443 and see how it goes.FCan you share the nginx logs with me?
Fwhat infra are you using?
upstream timeout means zitadel does not reply in time
upstream timeout means zitadel does not reply in time
Fand I have not seen that happen many times 
Fso:
1) Zitadel or the DB have to liitle resources (which is hard to believe)
2) Nginx upstrem timeout is configured too low
1) Zitadel or the DB have to liitle resources (which is hard to believe)
2) Nginx upstrem timeout is configured too low
FI think for this we can ignore them.
Sizing wise looks fine for a small env. Can you share what upstream timeouts you have configured?
Sizing wise looks fine for a small env. Can you share what upstream timeouts you have configured?
Fhm, but would this not mean zitadel takes more then 600s for a response (which would be way to slow)
FHow does the CPU look like on the database and zitadel vm
FSo it only happens on the OTP call, right?
What happens if you increase the values to 6000?
What happens if you increase the values to 6000?
F(not to say that this is correct but a verification)
FHehe yeah it is weird, I have not seen this so far
FHm do me this looks like a weird connectivity issue.
Is the nginx on the same machine as zitadel?
Is the nginx on the same machine as zitadel?
FCan you share me the full logs. of zitadel and nginx?
FHm there is a weird db connection error. But I am not sure this correlates.
Interesting the 504 is printed on the callback from an externalIDP redirect, I thought it was on the OTP page?
Interesting the 504 is printed on the callback from an externalIDP redirect, I thought it was on the OTP page?
SHas this been solved? Facing exact same issue but on cloudrun with cloud sql and using either github idp and logging in or entra id and logging in
SHey, we solved this with having private ips only cause egress went to serverless vpc. So our bad 
FHm, you mean like traffic went through a nat gateway or something like that?