504 internal server error on teleport 13+ (nginx loadbalancer) #48895
Unanswered
Giannischri
asked this question in
Q&A
Replies: 2 comments
-
|
Greetings, Teleport 13 is no longer maintained and v14 is about to be EOL. Please try this on more recent versions and confirm if you are still seeing this. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Do you have mixed IPv4 and IPv6 clients in your environment? I see this same issue when native IPv6 clients try to connect to my cluster (which is on IPv4 only) through Cloudflare. What shows in the log files for the Teleport auth/proxy service when you see the 504 error? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have nginx loadbalancer and cloudflare configuration...i am following the teleport 13+ guide for the values inside the teleport cluster helm chart....when users get their invite tokens and register they get a 504 internal server error immediately after registering.Some users have managed to get access while others (especially macos users) couldnt
Beta Was this translation helpful? Give feedback.
All reactions