-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ISSUE] Identity module UI throwing 502 Bad Gateway #707
Comments
What is the status of the Identity pods?
|
The identity module is running when looked from pod even when trying open ui it redirects to keycloak but afte sign it gives 502 Bad Gateway error |
@ikomalchauhan please share the values file because the Identity Pod looks good, so it could be a misconfiguration. |
@ikomalchauhan Did you ever find a resolution for this? I have a similar issue with Identity due to a failing health check with GKE ingress-gce -> #788 |
Describe the issue:
I have installed the latest helm chart using 8.2.5 tag for images. All the components works fine including identity with other modules, but when I am calling identity UI, post Keycloak authentication I am getting 502 Bad Gateway error.
Actual behavior:
Post Keycloak authentication I am getting 502 Bad Gateway error in Identity UI.
Expected behavior:
Identity UI shold be accessable
How to reproduce:
USe the HELM chart camunda-platform-8.2.4 using custom Keycloak
Logs:
No Error found in identity modules logs.
Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.
The text was updated successfully, but these errors were encountered: